From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@robin.gentoo.org
Subject: Re: [gentoo-portage-dev] RFC: Binary dependency tracking
Date: Wed, 6 Apr 2005 02:23:04 -0500 [thread overview]
Message-ID: <20050406072304.GB13607@exodus.wit.org> (raw)
In-Reply-To: <1112740704.31455.20.camel@cid.outersquare.org>
On Tue, Apr 05, 2005 at 03:38:24PM -0700, Jeremy Huddleston wrote:
> Well, I've glossed over the dlopen() issues for now as I'm not sure the
> best way to handle that or even if it needs to be addressed. How often
> does something dlopen() a file if it doesn't know the exact filename at
> compile time?
> It seems unlikely to me that this kind of dependency
> would be introduced which wouldn't be uniquely satisfied by the RDEPEND.
> Does anyone know of a case where we'd do something like:
>
> #define LIBPNG_SONAME libpng.so.3 /* set by configure */
> dlopen(LIBPNG_SONAME)
kdelibs apps abuse it afaik.
rekall, fex, loads all drivers dependant on config files, all at
runtime via abstracted dlopen trickery....
>
> In any event, here's a patch to portage which creates the
> soname.{PROVIDE,DEPEND} files as well as a small script to create them
> where missing.
>
> Please comment.
Not liking it in bash personally, but that's me (already implemented
code akin to this in dblink.treewalk).
What about the resolver mods?
~brian
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-06 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1110961726.2948.72.camel@cid.outersquare.org>
[not found] ` <20050316181919.GC31829@freedom.wit.com>
[not found] ` <200503162102.25494.pauldv@gentoo.org>
2005-04-05 22:38 ` [gentoo-portage-dev] RFC: Binary dependency tracking Jeremy Huddleston
2005-04-06 7:23 ` Brian Harring [this message]
2005-04-06 10:12 ` Paul de Vrieze
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=20050406072304.GB13607@exodus.wit.org \
--to=ferringb@gentoo.org \
--cc=gentoo-portage-dev@gentoo.org \
--cc=gentoo-portage-dev@robin.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