public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paul Smith" <pausmith@nortelnetworks.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Portage choosing wrong version?
Date: Thu, 12 Feb 2004 13:00:58 -0500	[thread overview]
Message-ID: <16427.48986.501829.428875@lemming.engeast.baynetworks.com> (raw)

Hi all.  I have a strange situation and I'm wondering if anyone can help
me understand it or give me tips on how to better understand it.

I'm using Portage (2.0.49) to manage a set of locally-constructed
ebuilds; these are not in the Gentoo system.

I'm installing them through a "collection" ebuild, which contains
nothing but a DEPENDS line, say collection-1.0.ebuild:

    DEPENDS=" ~category/foo-1.0 ~category/bar-1.0 ~category/baz-1.0 "

In my packages file I say:

    * ~category/collection-1.0


Also the bar-1.0 and baz-1.0 packages depend on foo and they both say
so, like this:

    DEPENDS=" category/foo "


Now, I also have a foo-1.1, bar-1.1, and baz-1.1.  The bar-1.1 and baz-1.1
packages depend on foo-1.1 and they both say so, like this:

    DEPENDS=" ~category/foo-1.1 "

However, I want to install the older 1.0 versions right now, not the
newer ones.


Now if none of these packages are installed and I run "emerge system",
something very bizarre happens: emerge _FIRST_ installs the latest
category/foo-1.1 package, then it tries to build the other packages,
which fail because they won't work with newer versions of foo!

Then, if I run "emerge -p system" I see that emerge will, later on,
replace the foo-1.1 it just installed with foo-1.0.


Doesn't Portage have enough smarts to realize that if the collection
package depends on a specific version and other packages depend on any
version, that it should just install the specific version to satisfy the
dependency relationship?

If not, this is very bad!  How can I work with this?  Surely I don't
have to go back to every old version and update all their DEPENDS lines
every time I come out with a new package which is not backward
compatible?


And, is there any command I can run or option I can use to get a more
detailed description of exactly how emerge is resolving dependency
relationships?


Thanks!

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@nortelnetworks.com>   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.

--
gentoo-portage-dev@gentoo.org mailing list


                 reply	other threads:[~2004-02-12 18:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16427.48986.501829.428875@lemming.engeast.baynetworks.com \
    --to=pausmith@nortelnetworks.com \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox