I see a lot of double-slashes in computed paths across many ebuilds. I know (from working with the zope,zope-config ebuilds) first-hand that keeping track of which path variables have trailing slashes is difficult. Portage should offer a standard function (e.g. epathclean) that takes a path variable and (at a minimum) removes any double-slashes. * After doing that, you can safely remove /usr//lib/libFLAC.so.4 * Note: 'emerge gentoolkit' to get revdep-rebuild The problem is that although bash seems to handle double-slashes gracefully, if they should make it to config files or other read-many locations, the program or language using these double-slash paths may behave quite differently. I think python is an example of this. I have had many problems that were related to double-slash paths originating in the ebuild. Use of this function should be added to the style guite, and perhaps some QA checks that I see portage is able to apply to ebuilds at runtime. Reproducible: Always Steps to Reproduce:
this is a hack the sources of the double slashes should be tracked down and fixed
Agreed for portage internals to. Specific instances? Go for it.
