%% Svyatogor <[EMAIL PROTECTED]> writes:

  s> That sounds strange to me :/ What about the output for emerge
  s> --pretend? It wouldn't show you the smae package in the list twice,
  s> will it?

Yep, it does show it twice.  Here's a -p output:

  $ emerge -p system

  These are the packages that I would merge, in order:

  Calculating system dependencies ...done!
  [ebuild  N    ] nt-libs/tenv-1.2.0 
  [ebuild  N    ] nt-libs/tableView-1.1.0 
  [ebuild  N    ] nt-libs/ioe-1.2 
  [ebuild  N    ] nt-libs/hwd-1.2 
  [ebuild  N F  ] net-misc/sri-snmp-15.4.1.4-r1 
  [ebuild  N    ] net-www/lynx-2.8.4.1c 
  [ebuild  N    ] nt-libs/sms-3.0.0 
  [ebuild  N    ] nt-sysapps/nameserver-1.6.0 
  [ebuild  N    ] nt-libs/ed-1.0 
  [ebuild  N    ] nt-libs/ndi-1.2 
  [ebuild  N    ] nt-libs/pca200e-1.0 
  [ebuild  N    ] net-libs/libpcap-0.7.2 
  [ebuild  N    ] nt-libs/ndi-1.1 
  [ebuild  N    ] dev-libs/boost-1.30.2 
  [ebuild  N    ] nt-libs/s514-1.0 
  [ebuild  N    ] net-analyze/ethereal-0.10.0a 
  [ebuild  N    ] nt-libs/ioe-1.1 
  [ebuild  N    ] app-arch/gzip-1.3.3-r2 
  [ebuild  N    ] nt-libs/hostEth-1.0 
  [ebuild  N    ] sys-devel/crosstools-ppc-bin-3.2.3-r2 
  [ebuild  N    ] nt-libs/jfk-0.6.1 
  [ebuild  N    ] nt-libs/df-1.1 
  [ebuild  N    ] nt-configs/mse-2.0 

Note here that ioe-1.2 is installed first, then later ioe-1.1 is
installed.  Also for ndi: ndi-1.2 is installed first then a few packages
later ndi-1.1 is installed.  The last package listed (mse-2.0) is the
wrapper package.  That one requests ioe-1.1 and ndi-1.1.

I just found the emerge --debug option so I'm also going to look
carefully at that output and see if I can figure out what's going on.


I'm _really_ curious to understand how Portage computes the
dependencies, in detail.  None of my hypotheses about how it might work
appear to fit the facts.  Is there any documentation on this, and/or
anyone on the list who has enough of an intimate knowledge to describe
it with some authority?

  s> The only workaround I can suggest is to mask all package versions
  s> which are higher than those needed by latest wrapper script...

Well, the thing is I want some systems to have an older version and
other systems to have a newer version, so modifying the ebuilds is not
really going to work.  Also changing packages files or similar is tricky
since it has to be done on many systems.  I really need to be able to
say "emerge wrapper-2.0" and get all the 2.0-based packages installed on
the system.

-- 
-------------------------------------------------------------------------------
 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

Reply via email to