public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC about another *DEPEND variable
Date: Thu, 21 Sep 2006 11:11:31 -0400	[thread overview]
Message-ID: <200609211111.31539.vapier@gentoo.org> (raw)
In-Reply-To: <1158850564.16173.97.camel@localhost>

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

On Thursday 21 September 2006 10:56, Duncan Coutts wrote:
> If we do go in this direction it'd be great to be able to slot on the
> ABI and still have dependencies resolved correctly. For example imagine
> having parallel python-2.3 and 2.4 installations with some libs
> installed for both. Crucially, deps need to be resolved to the version
> of a lib with the right ABI.

ugh, no ... we are not a binary distribution so we should not have to worry 
about ABI baggage

we SLOT based upon API, not ABI
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2006-09-21 15:17 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 [this message]
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=200609211111.31539.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