From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC about another *DEPEND variable
Date: Thu, 21 Sep 2006 20:24:32 +0300 [thread overview]
Message-ID: <4512CAD0.2090800@gentoo.org> (raw)
In-Reply-To: <200609211046.08597.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Mike Frysinger wrote:
> i think you're merging the two issues you brought up ... there is binary ABI
> issues (which should not require a new DEPEND variable as portage can extract
> that information out at runtime) and there is runtime plugin issues with
> packages using dlopen() (which portage cannot extract as the dependency
> cannot ever be extracted)
>
Okay, maybe I hijacked BINCOMPAT purpose. As I said in a previous reply,
my original message was about runtime compatibility, not compilation
compatibility.
I want to be able to save in a package metadata that it was build using
some version (as in compatibility version, not necessarily PV) of
another package and I want emerge to automatically rebuild my package
whenever this version is changed.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-09-21 17:27 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
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 [this message]
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=4512CAD0.2090800@gentoo.org \
--to=mrness@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