| 1 |
On Sunday 29 February 2004 03:46, Jeremy Huddleston wrote: |
| 2 |
> On Sat, 2004-02-28 at 02:55, Stuart Herbert wrote: |
| 3 |
> > I agree with Jason - a config file that hasn't been modified shouldn't be |
| 4 |
> > config-protected. No information is lost when the file is removed, and |
| 5 |
> > if a Gentoo user has edited the file, it'll get picked up because of the |
| 6 |
> > change in timestamp and md5sum. |
| 7 |
> |
| 8 |
> It should be left. Consider this case: |
| 9 |
> $ emerge packageA |
| 10 |
> /etc/services is modified to contain a reference for packageA |
| 11 |
> |
| 12 |
> $ emerge packageB |
| 13 |
> /etc/services is modified to contain a reference for packageB |
| 14 |
> |
| 15 |
> $ emerge unmerge packageB |
| 16 |
> say good bye to /etc/services |
| 17 |
|
| 18 |
I don't have any packages owning /etc/services. It may be that I don't have |
| 19 |
any packages installed that have modified it, but I believe it's because |
| 20 |
packages that modify it do so in either pkg_postinst() or pkg_config(). |
| 21 |
|
| 22 |
I have hotwayd installed which warned me in pkg_postinst() and with a little |
| 23 |
checking I found glftpd will modify it in pkg_config(). Any package which |
| 24 |
copies something in /etc to its image and then modifies it to be integrated |
| 25 |
with etc-update is bad form imho. |
| 26 |
|
| 27 |
Regards, |
| 28 |
Jason Stubbs |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives