From: "Jesus Rivero (Neurogeek)" <neurogeek@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Auto dependency builder progress report. Week 7.
Date: Fri, 15 Jul 2011 16:08:42 -0400 [thread overview]
Message-ID: <CAD3zpD=6-D1Q4fDyPmoA4O7ZWG=T3e9pmAedScsp1NSckjTV4A@mail.gmail.com> (raw)
In-Reply-To: <20110715185431.GJ2828@comet.mayo.edu>
On Fri, Jul 15, 2011 at 2:54 PM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> 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.
>
RDEPEND will be tricky to get right, but I like this approach, could
work for those packages with tests.
We are going to discuss an approach for this and for the filtering of
@system, as we need to find a way to get rid of second-hand deps.
> --
> Thanks,
> Donnie
>
> Donnie Berkholz
> Admin, Summer of Code
> Gentoo Linux and X.Org
> Blog: http://dberkholz.com
>
>
--
Jesus Rivero (Neurogeek)
Gentoo Developer
prev parent reply other threads:[~2011-07-15 20:08 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
2011-07-15 20:08 ` Jesus Rivero (Neurogeek) [this message]
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='CAD3zpD=6-D1Q4fDyPmoA4O7ZWG=T3e9pmAedScsp1NSckjTV4A@mail.gmail.com' \
--to=neurogeek@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