| 1 |
Thomas de Grenier de Latour wrote: |
| 2 |
> On Sat, 28 Jan 2006 18:58:52 -0800 |
| 3 |
> Donnie Berkholz <spyderous@g.o> wrote: |
| 4 |
> |
| 5 |
>> You want people to recompile the whole package to get another |
| 6 |
>> text file installed? |
| 7 |
> |
| 8 |
> When would one recompile a package just for that? Only case i can |
| 9 |
> think of is when someone who already has setup his apache / ftp / |
| 10 |
> database / whatever server suddenly discover what "logrotate" is |
| 11 |
> and thus decide to start using it, whereas until then he didn't |
| 12 |
> payed any attention to the flag each time it was listed by "emerge |
| 13 |
> -pv". That sounds rather unlikely, and i would say "too bad, be |
| 14 |
> more careful next time..." to such a sysadmin. And anyway, this |
| 15 |
> user doesn't really have to recompile anything to fix his mistake: |
| 16 |
> he can still have a look on the ebuild to see that if the file he |
| 17 |
> is missing is available in $FILESDIR, or use "ebuild unpack" and |
| 18 |
> get it from the sources tree when it comes from upstream. |
| 19 |
> |
| 20 |
[snip] |
| 21 |
|
| 22 |
indeed, rephrasing what sayd before in the same thread: |
| 23 |
|
| 24 |
Mysql eclass will add a USE flag, local or global, "logrotate" for next |
| 25 |
versions of MySQL, not touching the old ebuilds. |
| 26 |
|
| 27 |
Run-time needed files will still live in $PORTDIR/dev-db/mysql/files, |
| 28 |
because their size is small, and they change seldom. Compile time needed |
| 29 |
files have been already moved in a separate SRC_URI fetched file. |
| 30 |
|
| 31 |
Unless we decide to drop totally "logrotate" use flag support. |
| 32 |
|
| 33 |
BTW hope this is not enough fuel to start another flamewar. |
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives