-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick Steeves wrote:
IMHO, this is SysV-esque clutter. CRUX's BSD-like filesystem layout seems cleaner to me, and it would be a shame to muddle it. Also, /etc is usually protected because that is /etc/pkgadd.conf's default. /usr/etc is usually overwritten with each release, which insures that the upgrade works out of the box. Isn't the latter preferable to the support nightmare of persistent configuration files which might be incompatible in some way with the upgraded API? Will rejmerge after every upgrade become a necessity which springs from this? Why not adopt portage and etc-update while we're at it...
My concern isn't about aesthetics at all, really. It's simply about software that doesn't work like you'd expect.
Attached is the gnome-menus Makefile from FreeBSD. Are those two sed lines enough to make gnome-menus do /usr/etc? Quite often I head over to freshports.org, in order to derive solutions/inspiration for a port I'm working on. Interestingly, graveman looks like a relatively normal port. I have a feeling the secret is in the "gnomehack" and "gnomeprefix". (http://www.freebsd.org/gnome/docs/gnome_porting.html) Maybe it's not worth the bother though...
As far as I can tell, those sed lines have absolutely zero to do with XDG. I'll take a look at a few other freebsd/whatever ports but this one isn't any particular indication. As for graveman, it IS a rather normal port. The problem is just a bug in its runtime behavior. Hopefully they'll fix it soon, though. Anyway, I'm not completely against the /usr/etc bit if we can get everything to play nicely but I suppose that will take time to figure out. - -- Matt Housh (jaeger@freenode/#crux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCe/mgGFVQ7mavvGgRApd+AKCyKRHHgOF33yQ3XI5H4ua0kz90cgCfQDyf IAUlFRB3+NMd5fp7bXtlHHE= =Udil -----END PGP SIGNATURE-----