| 1 |
On Sun, 29 Jan 2006 13:51:25 -0800 |
| 2 |
Donnie Berkholz <spyderous@g.o> wrote: |
| 3 |
|
| 4 |
> Thomas de Grenier de Latour wrote: |
| 5 |
> > Or again another one (a bit ugly imho tho): merge the files in |
| 6 |
> > an "/etc/logrotate.d.dist" directory, and add an eselect module |
| 7 |
> > to handle symlinks from "/etc/logrotate.d". |
| 8 |
> |
| 9 |
> What's ugly about this? I like it. |
| 10 |
> |
| 11 |
|
| 12 |
What i fear could be a bit ugly is transition of existing systems |
| 13 |
from the current setup (logrotate.d/files) to the eselect setup |
| 14 |
(logrotate.d/symlinks -> logrotate.d.dist/files). I don't really see |
| 15 |
how to automate that since it would require being able to make |
| 16 |
distinction beetween packages' files and users' files (to move the |
| 17 |
first ones but not the second ones), and i don't really like the |
| 18 |
idea to do that kind of nasty tricks in some pkg_*inst function or |
| 19 |
alike. That, and also the fast transition on ebuilds side would |
| 20 |
somehow need to happen all at the same time so that no ebuild |
| 21 |
continue to put real files in logrotate.d once a system is on an |
| 22 |
select setup. |
| 23 |
It would be interesting to know how that happened for in the past |
| 24 |
for /etc/bash_completion.d, which made a similar move iirc |
| 25 |
(although real files went to /usr/share/something, whereas here i |
| 26 |
would rather see them in etc because they are more likely to be |
| 27 |
customized). |
| 28 |
|
| 29 |
-- |
| 30 |
TGL |
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives