From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] wxGTK {up|down}grade loop
Date: Sat, 25 Oct 2003 22:00:25 +0200 [thread overview]
Message-ID: <200310252201.05141.pauldv@gentoo.org> (raw)
In-Reply-To: <3F9AB9C4.70506@technaut.darktalker.net>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1044 bytes --]
> 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.
To fix this problem we need a dependency checker that works with the whole
installed tree, and validates it. We currently don't have such a checker and
the current checker cannot be adapted to do that either. The problem is that
it is very hard to make a checker to do forward and backward dependency
checking and still being efficient.
We are working on this, and it is certainly high on our list of desired
features, but currently there is not much to fix this.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-25 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 17:43 [gentoo-dev] wxGTK {up|down}grade loop Ruben Vermeersch
2003-10-25 17:58 ` Andrew Gaffney
2003-10-25 20:00 ` Paul de Vrieze [this message]
2003-10-25 20:23 ` Andrew Gaffney
2003-10-25 20:39 ` Paul de Vrieze
2003-10-25 20:58 ` Paul de Vrieze
2003-10-25 23:17 ` Grant Goodyear
2003-10-27 6:11 ` Andrew Gaffney
[not found] ` <20031025200632.GA5274@whitestar>
2003-10-27 6:01 ` Andrew Gaffney
2003-10-25 18:16 ` Brian Jackson
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=200310252201.05141.pauldv@gentoo.org \
--to=pauldv@gentoo.org \
--cc=gentoo-dev@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