Discussion, talk and tips
https://forum.puppylinux.com/
Hi.
In Woof-CE script 3builddistro at line 258:
EXTRAS_LIST="${ADRV_INC// /|} ${YDRV_INC// /|} ${AFDRV_INC// /|}"
What is that (the red one) ?
I don't think it would be possible to add an afdrv .sfs to Puppy, no?
It seems not to be used in all the Woof-CE scripts.
taersh wrote: ↑Sat Mar 20, 2021 3:11 amHi.
In Woof-CE script 3builddistro at line 258:
EXTRAS_LIST="${ADRV_INC// /|} ${YDRV_INC// /|} ${AFDRV_INC// /|}"
What is that (the red one) ?
I don't think it would be possible to add an afdrv .sfs to Puppy, no?It seems not to be used in all the Woof-CE scripts.
If not intended somehow, then maybe a typo/error and should be ${FDRV_INC// /|}?"
adrv support works, look at fossa64.
This testing build has a functional adrv - https://github.com/dimkr/woof-CE/releas ... 9.499-adrv
This ugly and unreadable loop takes a list of packages like "abiword gnumeric" and converts it into "abiword|gnumeric", then passes that through grep, so it filters lines containing one of the package names.
This area had a bug I fixed recently, in https://github.com/puppylinux-woof-CE/w ... 2135/files. 3builddistro didn't filter out comments, so lines containing the word "abiword" in a comment got ignored, and gmp (a dependency of GCC) didn't get added to rootfs-complete, breaking fossa64.
Make sure on you're on the latest woof-CE (git pull), it's fixed now.
EDIT: ha, this typo can break fdrv, not adrv.