public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Mylchreest <johnm@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [Fwd: Re: [gentoo-dev] How to handle conflicts?]
Date: 16 Jun 2003 12:13:09 +0100	[thread overview]
Message-ID: <1055761989.28763.23.camel@johnm.willow.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

forwarding my reply onto the list as well.

> > 
> > What is the best way to handle conflicts of packages? Ie: I have a
> > stable (release) version of software A, and I also have a bleeding edge
> > version of the same software (that tracks the same current stable
> > version). What I want to do is that if they install the CVS version (or
> > the release version) they can't install the other version without
> > un-installing the other one. I'd like to do this to make sure that they
> > are linked against the correct version of the libraries.
> > 
> > Best regards
> >  Michael Boman
> 
> You can put blocking packages into the DEPEND.
> please check gaim and gaim-cvs for examples :)
> 
> 
> -- 
> John Mylchreest.
> Gentoo Linux Developer
> 
> Gentoo Linux:	http://www.gentoo.org
> Public Key:	gpg --recv-keys 0xEAB9E721
> 		http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xEAB9E721
> 
> Key fingerprint:0670 E5E4 F461 806B 860A  2245 A40E 72EB EAB9 E721
-- 
John Mylchreest.
Gentoo Linux Developer

Gentoo Linux:	http://www.gentoo.org
Public Key:	gpg --recv-keys 0xEAB9E721
		http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xEAB9E721

Key fingerprint:0670 E5E4 F461 806B 860A  2245 A40E 72EB EAB9 E721

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-06-16 11:13 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=1055761989.28763.23.camel@johnm.willow.local \
    --to=johnm@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