Trenton Adams schreef: > On 1/5/06, Tom Martin <[EMAIL PROTECTED]> wrote: > >> On Thu, 5 Jan 2006 00:29:57 -0700 Trenton Adams >> <[EMAIL PROTECTED]> wrote: >> >> >>> Ok, so I get the output below when trying to merge after a sync >>> today. My guess is that the openmotif package was made into two >>> separate packages, correct? >>> >>> To the portage developers, how could this be handled? Perhaps >>> emerge could somehow figure out the reason for such a conflict, >>> and then automatically unmerge the original package? >> >> Not really a question to the portage developers -- just unmerge >> openmotif (the blocker) and continue as normal. > > > So what happens to the unknowing user that doesn't figure out that > the package was split into multiple packages? Especially if it's a > critical system package. They may not like the idea of unmerging the > package, and re-merging. > >
You actually don't have to 're-merge'; the openmotif upgrade will be installed by motif-config. This is actually standard operating procedure; the normal way to resolve the vast majority of blocks is to unmerge the package that is blocking something. The fact that one (installed) package blocks another (to-be-installed) package is almost always because the to-be-installed package replicates the functionality of the currently-installed package, contains it, or the currently-installed package must be specifically installed as a dependency of the to-be-installed package. Sometimes the issue is that the to-be-installed package breaks with the currently-installed package remaining installed. But in all of these cases, the solution is to unmerge the blocking package, and then trust Portage (and the devs) to sort everything out so that you don't lose any functionality. This trust is 98% of the time well-placed. Holly -- gentoo-user@gentoo.org mailing list
