public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [Fwd: Re: [gentoo-dev] How to handle conflicts?]
@ 2003-06-16 11:13 John Mylchreest
  0 siblings, 0 replies; only message in thread
From: John Mylchreest @ 2003-06-16 11:13 UTC (permalink / raw
  To: gentoo-dev

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-06-16 11:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-06-16 11:13 [Fwd: Re: [gentoo-dev] How to handle conflicts?] John Mylchreest

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox