public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vitaly Kushneriuk <vitaly_kushneriuk@yahoo.com>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] qpkg
Date: 13 Jan 2002 21:12:20 +0200	[thread overview]
Message-ID: <1010949140.3345.7.camel@uranus.u235.eyep.net> (raw)
In-Reply-To: <20020113115355.X62855-100000@ozma.union.utexas.edu>

> Perhaps, though, qpkg should not flag major revisions as duplicates.  For
> instance, qpkg flags the following packages as duplicates:
> 
> x11-libs/qt-2.3.1
> x11-libs/qt-3.0.1
> media-libs/freetype-2.0.5-r1
> media-libs/freetype-1.3.1-r3
> sys-devel/automake-1.4_p5
> sys-devel/automake-1.4-r2
> 
> The first two sets are not duplicates because they are incompatible major
> versions. The dbm libraries also have this issue (there are three major
> versions in common use, though I'm not sure what's included with gentoo.)
> I have no idea what to do about the last set - it's not possible to tell
> by the name which is more recent (I'm not sure how I got into this
> situation either!)
I think it's not "The Right Thing (tm)" to make qpkg
handle freetype/db/qt libraries as a special cases.
Having multiple UNcompatible versions of the same PACKAGE
(note: not library) will interfere with a lot of other stuff.
Consider something like "--autounmerge" options(I'd like to see
something like this in portage btw.) that would unmerge old version
if newer version successfully installed.
The proper way IMHO would be to split freetype into freetype and
freetype2, removing all conflicts. The same aplies to db/db2/db3 etc.
This is the standard way of dealing with such stuff I think.
I can add some exceptions list to qpkg, though, if freetype maintainer
(Daniel?) does not want to split it.



  parent reply	other threads:[~2002-01-13 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 14:46 [gentoo-dev] qpkg John Stalker
2002-01-13 15:38 ` Vitaly Kushneriuk
2002-01-13 17:39   ` Miguel Sousa Filipe
2002-01-13 19:02     ` Vitaly Kushneriuk
2002-01-13 18:01   ` Brent Cook
2002-01-13 18:02     ` Bart Verwilst
2002-01-13 19:12     ` Vitaly Kushneriuk [this message]
2002-01-13 18:03   ` Charles Kerr
2002-01-13 18:48     ` Vitaly Kushneriuk

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=1010949140.3345.7.camel@uranus.u235.eyep.net \
    --to=vitaly_kushneriuk@yahoo.com \
    --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