| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Robin H. Johnson wrote: |
| 5 |
> On Fri, Apr 29, 2005 at 09:36:54AM +0900, Jason Stubbs wrote: |
| 6 |
> |
| 7 |
>>What about the unused `ebuild [ebuild] config`? Isn't that the perfect place |
| 8 |
>>for this sort of stuff? The only package that I know that uses this feature |
| 9 |
>>is mysql. There are way more possibilities. |
| 10 |
> |
| 11 |
> No, ebuild config shouldn't be abused like this. Say I have an existing |
| 12 |
> install of mysql, and the package maintainer puts in an updated |
| 13 |
> logrotate.d file. Running 'ebuild mysql.ebuild config' is meant for NEW |
| 14 |
> installations only, and it doesn't enable me to take advantage of |
| 15 |
> CONFIG_PROTECT. I've seen a package where running the config phase when |
| 16 |
> the package is already set up blows away your existing config. It gives |
| 17 |
> you a warning first, but how would I then get an updated logrotate.d |
| 18 |
> file? |
| 19 |
> |
| 20 |
> I see only two viable options. |
| 21 |
> - Unconditional, use INSTALL_MASK, no RDEPEND on logrotate |
| 22 |
> - Conditional on USE=logrotate |
| 23 |
> |
| 24 |
> The first one is what is generally used in the tree so far. |
| 25 |
|
| 26 |
Seems like your third viable option is allowing CONFIG_PROTECT to work |
| 27 |
in the config step. |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFCcohMXVaO67S1rtsRAl0bAJ9LyXaXqg6Ii11wCjVAIshXibfneACgw4oN |
| 32 |
MiWRaEkmajAwl2Adg9KtGTA= |
| 33 |
=bSFX |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives