On Fri, Apr 29, 2005 at 09:36:54AM +0900, Jason Stubbs wrote: > What about the unused `ebuild [ebuild] config`? Isn't that the perfect place > for this sort of stuff? The only package that I know that uses this feature > is mysql. There are way more possibilities. No, ebuild config shouldn't be abused like this. Say I have an existing install of mysql, and the package maintainer puts in an updated logrotate.d file. Running 'ebuild mysql.ebuild config' is meant for NEW installations only, and it doesn't enable me to take advantage of CONFIG_PROTECT. I've seen a package where running the config phase when the package is already set up blows away your existing config. It gives you a warning first, but how would I then get an updated logrotate.d file?
I see only two viable options. - Unconditional, use INSTALL_MASK, no RDEPEND on logrotate - Conditional on USE=logrotate The first one is what is generally used in the tree so far. -- Robin Hugh Johnson E-Mail : [EMAIL PROTECTED] Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgpBmMMJ0J9ZF.pgp
Description: PGP signature
