I just noticed this recently, but perhaps previous versions of portage
had the same behavior.
A practiced I developed when using redhat for years was to place all
modified config files (e.g. /etc/postfix/main.cf) on a separate
filesystem /local (/local/etc/postfix/main.cf) and leave a symlink in
the root filesystem
(/etc/postfix/main.cf-->/local/etc/postfix/main.cf).
Then when a new release came out I would go through /local and
re-establish the symlinks, putting in changes as needed.
(A very few files like /etc/fstab must be on the root filesystem so I
treated them specially.)
My last emerge of baselayout (I believe done with the new portage)
resulted in a number of my symlinks being replaced with the new
files. For example /etc/conf.d/net had the new file and my
/local/etc/conf.d/net remained but was not linked to. Moreover, no
._*nnn file was produced so etc-update did not find the change (I
never use -3 or -5).
Is this a bug with the new portage or I have somehow not noticed the
feature before. Specifically,
1. Should an emerge replace a symlink with an ordinary file?
2. Should a ._*nnn file be produced?
The current behavior is "yes" and "no". I am glad that portage didn't
leave the link and silently change the target of the link.
I realize that gentoo is not "released-based" as was redhat, so
perhaps my practice is inappropriate. But I still believe that, in the
situation described above, a ._*nnn file should be produced.
Thanks,
allan
--
gentoo-user@gentoo.org mailing list
had the same behavior.
A practiced I developed when using redhat for years was to place all
modified config files (e.g. /etc/postfix/main.cf) on a separate
filesystem /local (/local/etc/postfix/main.cf) and leave a symlink in
the root filesystem
(/etc/postfix/main.cf-->/local/etc/postfix/main.cf).
Then when a new release came out I would go through /local and
re-establish the symlinks, putting in changes as needed.
(A very few files like /etc/fstab must be on the root filesystem so I
treated them specially.)
My last emerge of baselayout (I believe done with the new portage)
resulted in a number of my symlinks being replaced with the new
files. For example /etc/conf.d/net had the new file and my
/local/etc/conf.d/net remained but was not linked to. Moreover, no
._*nnn file was produced so etc-update did not find the change (I
never use -3 or -5).
Is this a bug with the new portage or I have somehow not noticed the
feature before. Specifically,
1. Should an emerge replace a symlink with an ordinary file?
2. Should a ._*nnn file be produced?
The current behavior is "yes" and "no". I am glad that portage didn't
leave the link and silently change the target of the link.
I realize that gentoo is not "released-based" as was redhat, so
perhaps my practice is inappropriate. But I still believe that, in the
situation described above, a ._*nnn file should be produced.
Thanks,
allan
--
gentoo-user@gentoo.org mailing list