From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC about another *DEPEND variable
Date: Sat, 23 Sep 2006 09:59:17 -0400 [thread overview]
Message-ID: <200609230959.17472.vapier@gentoo.org> (raw)
In-Reply-To: <200609230950.13347.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Saturday 23 September 2006 09:50, Mike Frysinger wrote:
> On Saturday 23 September 2006 09:14, Brian Harring wrote:
> > We don't classify our deps as actual build depends vs link depends; as
> > such trying to (essentially) "patch things up after" allow for the
> > scenario where merging breaks the toolchain, thus building isn't
> > possible.
>
> huh ? RDEPEND is linktime ... see my statement above
lemme rephrase ... you keep the ABI SONAME lib around until all packages are
done with it; this does not affect any other package (including upgrades to
the same package) as the ABI filename is unique in the filesystem
it is not used at linktime because it does not provide a linkable file ... it
merely provides the library used at runtime
so you can upgrade on the fly as the old ABI lib does not conflict with
anything
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-09-23 14:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 10:35 [gentoo-dev] RFC about another *DEPEND variable Alin Nastac
2006-09-21 11:38 ` Luca Barbato
2006-09-21 11:59 ` Brian Harring
2006-09-21 13:52 ` Mike Frysinger
2006-09-21 14:04 ` Brian Harring
2006-09-21 14:43 ` Mike Frysinger
2006-09-21 15:08 ` Brian Harring
2006-09-23 10:20 ` Mike Frysinger
2006-09-23 13:14 ` Brian Harring
2006-09-23 13:50 ` Mike Frysinger
2006-09-23 13:59 ` Mike Frysinger [this message]
2006-09-23 14:30 ` Brian Harring
2006-09-24 3:31 ` Mike Frysinger
2006-09-25 18:16 ` Brian Harring
2006-09-27 6:24 ` Mike Frysinger
2006-09-27 7:54 ` Brian Harring
2006-09-30 18:01 ` Mike Frysinger
2006-09-30 19:34 ` Brian Harring
2006-10-02 12:53 ` Mike Frysinger
2006-09-21 14:14 ` Donnie Berkholz
2006-09-21 14:40 ` Mike Frysinger
2006-09-21 14:54 ` Donnie Berkholz
2006-09-21 15:01 ` Mike Frysinger
2006-09-24 2:36 ` Ciaran McCreesh
2006-09-24 3:13 ` Mike Frysinger
2006-09-21 14:56 ` Duncan Coutts
2006-09-21 15:10 ` Simon Stelling
2006-09-21 15:11 ` Mike Frysinger
2006-09-21 15:41 ` Duncan Coutts
2006-09-21 18:27 ` Luca Barbato
2006-09-21 21:34 ` Duncan Coutts
2006-09-21 23:25 ` Luca Barbato
2006-09-23 10:13 ` Mike Frysinger
2006-09-23 10:35 ` Duncan Coutts
2006-09-23 10:52 ` Mike Frysinger
2006-09-21 14:38 ` Alin Nastac
2006-09-21 14:46 ` Mike Frysinger
2006-09-21 17:24 ` Alin Nastac
2006-09-21 14:51 ` Brian Harring
2006-09-21 17:15 ` Alin Nastac
2006-09-21 19:51 ` Brian Harring
2006-09-23 10:05 ` Mike Frysinger
2006-09-23 14:24 ` Alin Nastac
2006-09-23 14:34 ` Mike Frysinger
2006-09-23 14:53 ` Brian Harring
2006-09-23 15:07 ` Mike Frysinger
2006-09-21 12:05 ` Alin Nastac
2006-09-21 13:50 ` Mike Frysinger
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=200609230959.17472.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.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