From: Michael Boman <michael.boman@securecirt.com>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] How to handle conflicts?
Date: 16 Jun 2003 19:06:44 +0800 [thread overview]
Message-ID: <1055761603.16104.17.camel@r2d2.dmz1.securecirt.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Hi,
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
--
Michael Boman
Security Architect, SecureCiRT Pte Ltd
http://www.securecirt.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-06-16 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 11:06 Michael Boman [this message]
2003-06-16 16:55 ` [gentoo-dev] How to handle conflicts? Zack Gilburd
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=1055761603.16104.17.camel@r2d2.dmz1.securecirt.com \
--to=michael.boman@securecirt.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