Bug 421165 – sys-apps/portage: unmerge orphan symlinks when CONTENTS lists directory instead

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Zac Medico 2012-06-14 21:15:00 UTC]

For example, skype-2.2.0.35-r99 installs a /usr/share/skype -> /opt/skype symlink, and skype-4.0.0.7-r1 installs /usr/share/skype as a directory. If skype-4.0.0.7-r1 gets installed on top of the symlink, we want that orphan symlink to be unmerged if skype is unmerged.

[Comment 1 Zac Medico 2012-06-15 23:44:01 UTC]

This is fixed in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0c29f1531fe9787cd1bd96fcd5c34ec5e6128aa4

[Comment 2 Zac Medico 2012-06-23 07:40:18 UTC]

This is fixed in 2.1.11 and 2.2.0_alpha111.

[Comment 3 Zac Medico 2012-06-23 10:27:53 UTC]

Since /lib is a symlink to /lib64 on my amd64 system, I'm getting a message like this when I rebuild my kernel modules:

 * One or more symlinks to directories have been preserved in order to
 * ensure that files installed via these symlinks remain accessible:
 * 
 *      /lib
 * 

I guess we can just whitelist /lib and /usr/lib here.

[Comment 4 Davide Pesavento (RETIRED) 2012-06-23 11:14:35 UTC]

(In reply to comment #3)
> I guess we can just whitelist /lib and /usr/lib here.

Sounds good.