public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] dynamic runtime dependencies
Date: Fri, 13 Feb 2004 14:01:49 +0100	[thread overview]
Message-ID: <200402131401.50261.pauldv@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi all,

various packages have detection scripts in their configure. Basically 
those scripts implement optional support. In many cases these configure 
scripts can be told to ignore an available lib. Some scripts however can 
not be told so.

What I would want your opinion on is a new variable (DYNRDEPEND) that 
contains a list of packages that will depended on when they are 
available at runtime. This would need to be implemented with logic to 
actually record the existence of those packages in the metadata for 
binary or installed packages.

I believe such a variable would make many packages more transparent and 
would allow for optional dependencies to be used in more cases. As such 
I think it will help avoiding bloat.

Paul

ps. As a sidenote it would be usefull with subversion which can build 
it's own apache2 libs when apache2 is not there. Currently it uses the 
apache2 useflag for this which has a number of drawbacks.

pps. This might also help in making useflags more clear or even against 
useflag hell (too many with different results)

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFALMq9bKx5DBjWFdsRAvHSAKC7jgMgyRk9elhgxGP+8oSbBirPVACfQ4b2
1vVhdKoV3gONFw2lCDZ2RqQ=
=xunR
-----END PGP SIGNATURE-----

--
gentoo-portage-dev@gentoo.org mailing list


                 reply	other threads:[~2004-02-13 13:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200402131401.50261.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --cc=gentoo-portage-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