%% Spider <[EMAIL PROTECTED]> writes:
>> That sounds strange to me :/ What about the output for emerge
>> --pretend? It wouldn't show you the smae package in the list twice,
>> will it? The only workaround I can suggest is to mask all package
>> versions which are higher than those needed by latest wrapper
>> script...
s> emerge -p system will always try to go for the -latest- version
s> around though, As will all of portage when you do "emerge foo" (it
s> will try to get the latest version, not just any version) So that
s> might be something to keep in mind.
Looking at the --debug output I can see (sort of) what happens. Take
the ndi-1.1 / ndi-1.2 issue from my previous mail.
The main package in the packages file (mse-2.0) depends on ndi-1.1 and I
see that listed in the Candidates: line:
..., '~nt-libs/ndi-1.1',...
Now later on, we have an ebuild that has DEPEND="nt-libs/ndi", with no
version. Here it says:
ebuild: nt-libs/pca200e-1.0
binpkg: None
Parent: ebuild /test/ nt-libs/pca200e-1
.0 merge
Depstring: nt-libs/classlibrary nt-libs/ndi !crosscompile? ( >=nt-devel/ntmk-1.3 )
nt-libs/classlibrary nt-libs/ndi
Candidates: ['nt-libs/ndi']
ebuild: nt-libs/ndi-1.2
Here, even though Portage already knows that I requested a _specific_
earlier version, 1.1, it still chooses the latest available version to
satisfy _this_ relationship. Then later on it will put back ndi-1.1.
This is why I'm trying to understand the Portage algorithm. I assumed
that Portage would consider all the available requests for a given
package and choose the most recent one _that fulfills all the
requests_. In that case, a DEPEND with no version specified would
really mean "I can accept any version". But that doesn't appear to be
how it works, as seen above. Instead, Portage seems to interpret a
DEPEND with no version specified as "I must have the latest version".
s> However, this bug might also be something to consider:
s> http://bugs.gentoo.org/show_bug.cgi?id=39707
Hm! This looks somewhat promising. I'll check out the patch.
However, note that even if I use "emerge =nt-configs/mse-2.0" rather
than "emerge system", I still get the incorrect behavior.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> HASMAT: HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
[EMAIL PROTECTED] mailing list
