public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Leverton <levertond@googlemail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project]  ABI deps and DEPEND labelling
Date: Tue, 19 Aug 2008 21:52:35 +0100	[thread overview]
Message-ID: <200808192152.35935.levertond@googlemail.com> (raw)
In-Reply-To: <g8fav8$j69$1@ger.gmane.org>

On Tuesday 19 August 2008 21:35:35 Steve Long wrote:
> Not really fussed about how it's resolved, so long as we get some sort of
> correct link dependency information (which compile-against is not.)

compile-against is designed mainly for packages that include each-other's 
headers, nothing to do with linking.  For example, some libX11 headers 
include xproto headers.  If a given package only contains a reference, say, 
<X11/Xlib.h>, and not anything from xproto, then it should only build-depend 
on libX11, but xproto still needs to be present at compile-time.  The only 
way to represent that currently is by making libX11 RDEPEND on xproto, 
meaning "libX11 is not fully-functional unless xproto is installed", but 
embedded people and the like would prefer something more fine-grained, 
effectively splitting the idea of "fully-functional" into "fully-functional 
at runtime" and "fully-functional at build-time".

What exactly do you mean by "link dependency information"?  How would you like 
the package manager treat a "link" dependency differently from any other 
build dependency?



  parent reply	other threads:[~2008-08-19 20:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 20:35 [gentoo-project] ABI deps and DEPEND labelling Steve Long
2008-08-19 20:45 ` Ciaran McCreesh
2008-08-21 15:54   ` [gentoo-project] " Steve Long
2008-08-21 16:07     ` Ciaran McCreesh
2008-08-23 15:06       ` [gentoo-project] " Steve Long
2008-08-19 20:52 ` David Leverton [this message]
2008-08-21 16:27   ` [gentoo-project] " Steve Long

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=200808192152.35935.levertond@googlemail.com \
    --to=levertond@googlemail.com \
    --cc=gentoo-project@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