[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] New global USE flag: logrotate
From:       Donnie Berkholz <spyderous () gentoo ! org>
Date:       2005-04-29 19:17:32
Message-ID: 4272884C.6070501 () gentoo ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robin H. Johnson wrote:
> 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.

Seems like your third viable option is allowing CONFIG_PROTECT to work
in the config step.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCcohMXVaO67S1rtsRAl0bAJ9LyXaXqg6Ii11wCjVAIshXibfneACgw4oN
MiWRaEkmajAwl2Adg9KtGTA=
=bSFX
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]