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