From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Auto dependency builder progress report. Week 7.
Date: Fri, 15 Jul 2011 13:54:31 -0500 [thread overview]
Message-ID: <20110715185431.GJ2828@comet.mayo.edu> (raw)
In-Reply-To: <CAPomEdydkwFvO2E6-hbamMy3AXkstatwQQEZp9V+=_5VagVeNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On 16:29 Fri 15 Jul , Александр Берсенев wrote:
> 2011/7/15 Donnie Berkholz <dberkholz@gentoo.org>:
> > For DEPEND rather than RDEPEND ones, we'll want to make sure they're
> > definitely listed in dependencies of the ebuild being used, rather
> > than any level.
>
> The main drawback of hooklib approach is an inability to track what
> files have been loaded while exec call(runtime libraries). Most
> RDEPENDS are naturally filtered here. Fusefs approach logs all file
> system events.
>
> This is a difficult problem to distinguish RDEPENDS from DEPENDS. If I
> look on files accessed I can say if the dependency is runtime, but I
> haven't general strategy. I should watch more building logs of various
> packages to find a way.
You might be able to use src_test for this. If a package is accessed in
src_test as well as src_configure/src_compile, it's RDEPEND. Clearly
this won't work when src_test isn't defined, but it's a start.
--
Thanks,
Donnie
Donnie Berkholz
Admin, Summer of Code
Gentoo Linux and X.Org
Blog: http://dberkholz.com
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-07-15 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 6:22 [gentoo-soc] Auto dependency builder progress report. Week 7 Александр Берсенев
2011-07-15 15:31 ` Donnie Berkholz
2011-07-15 16:29 ` Александр Берсенев
2011-07-15 18:54 ` Donnie Berkholz [this message]
2011-07-15 20:08 ` Jesus Rivero (Neurogeek)
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=20110715185431.GJ2828@comet.mayo.edu \
--to=dberkholz@gentoo.org \
--cc=gentoo-soc@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