7 |
See, it's not possible to avoid that with the current Portage version. Installing an ebuild, which installs files previously provided by ebuilds of another package results in an error, when you have FEATURES=collision-protect set. In such a case, it's a bug not to add this blocking dependency (and of course you have to add it mutually to the affected ebuilds) - as ugly as it is. And before you say, "Fine, lets add RESTRICT=collision-protect to this particular ebuild."; This doesn't work either, because you never know, when - or to which future version - a user will actually perform the update. |