I wouldn't recommend this approach. This will probably break whatever package depends on the older version of the flip-flopping package.

Paul Fraser wrote:
You could use emerge -UDp instead, which will tell Portage to ignore any downgrades that may occur, and only show packages that will actually be updated.

On Sat, Oct 25, 2003 at 12:58:28PM -0500, Andrew Gaffney wrote:

Ruben Vermeersch wrote:

Ok, here's what's bugging me lately:

[EMAIL PROTECTED] ruben $ emerge -uDp world
These are the packages that I would merge, in order:
Calculating world dependencies ...done!
[ebuild U ] x11-libs/wxGTK-2.4.1-r1 [2.4.0]


After updating wxGTK, i stumble upon this:

neferteti ruben # emerge -uDp world
These are the packages that I would merge, in order:
Calculating world dependencies ...done!
[ebuild UD] x11-libs/wxGTK-2.4.0 [2.4.1-r1] Something tells me this ain't normal behaviour :)

I've seen this kind of thing a few times before, most notably with avifile and drip. In this case, there is an update available for wxGTK, so portage upgrades it. Unfortunately, there is some program installed that requires on a version of wxGTK <=2.4.0, so portage downgrades it to not break the other program. I consider this behavior a portage bug, but as far as I know, there is currently no easy way to prevent this from happening.


--
Andrew Gaffney


-- [EMAIL PROTECTED] mailing list




--
Andrew Gaffney


-- [EMAIL PROTECTED] mailing list



Reply via email to