Maybe this is already there but I don't remember seeing it in the portage changelogs I religiously check before upgrading, couldn't find any mention in the portage or make.conf manpages, and didn't see anything similar in a bug search, so... Grep /did/ find it in portage's vartree.py, so I know it's portage. This message would seem to be a relatively new feature as I think I only recently started getting it: * One or more symlinks to directories have been preserved in order to * ensure that files installed via these symlinks remain accessible. This * indicates that the mentioned symlink(s) may be obsolete remnants of an * old install, and it may be appropriate to replace a given symlink with * the directory that it points to. * * /var/log * /var/run Yes, they're symlinks, /var/run as the legacy location now pointing to /run, and /var/log a local installation quirk, pointing at /lg (shorter to type, I'd have used /l, but that's /usr/local! =;^). But the repeated notices get annoying after awhile! I like having the notice and believe it already alerted me to a stale symlink that I was able to remove, so it's certainly useful, but could there please be a (user configurable) list of symlinks it can shutup about? Presumably it'd be either a make.conf var or a symlinks.ignore file in /etc/portage. That would accomplish two things: 1) Admins would have a way to tell portage not to yell about specific symlinks. 2) The centralized location for such a list would give admins a place to track such symlinks too, adding explanatory comments, etc, so they don't end up wondering what in the world they were thinking, a year later when they try to figure out what it's doing there, why no packages claim it, etc... (I've developed the habit of putting a dated comment in my package.* files when I add an entry. It definitely helps me figure out those package.use settings I made just to work around this or that bug in a particular especially pre-release package version... a year and two more pre-releases and a stable version later! Since I use make.conf's includefile feature, even if it's a make.conf variable instead of a separate file, for me, it'd be a separate file, and I'd extend my comment habit to it.) As usual, thanks for the hard work and the often surprisingly quick responses/fixes. Sometimes people dump on portage but I'll say one thing, /most/ packages don't get the responsive maintainer and upstream that portage has, and I for one surely appreciate it! =:^)
You can set the UNINSTALL_IGNORE variable in make.conf like this: UNINSTALL_IGNORE="${UNINSTALL_IGNORE} /var/log /var/run"
*** Bug 428082 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 428082 ***
