> Yes, of course. The Task can just 'source' gobohide.conf and append
> the extra entries to the operation. I can do that later, or you can
> make your commits to the package, in the same way as the kernel
> modules are handled in the UserDefinedModules array at
BootOptions /
> BootScripts/BootUp.
>
My idea was that all directories should be selected from the .conf
file,
not just the extras, to ensure full customability (is that a
word? :) )
I don't see that as an advantage, as there's always a static "base"
which is going to be hidden. If one don't want some entry from that
base to be hidden, just take it out from the task.
...and then the next time you update, it's right back in there. On
Mac OS X, I had all the FHS stuff unhidden. There's much less of a
reason to do that with Gobo, but I can still see how people
(particularly FHS purists) might want it.
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
