From: Dale <rdalek1967@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: rfc: news item for png15
Date: Fri, 14 Oct 2011 18:39:33 -0500 [thread overview]
Message-ID: <4E98C835.7080606@gmail.com> (raw)
In-Reply-To: <1318634452.16741.0.camel@belkin4>
Pacho Ramos wrote:
> El vie, 14-10-2011 a las 16:48 -0500, Dale escribió:
>> Pacho Ramos wrote:
>>> It shouldn't, I am sure I have used this some times before and it
>>> worked as expected, but I don't know when revdep-rebuild cache files
>>> are removed (and then, broken packages recalculated) :-/ Any
>>> revdep-rebuild maintainer here to clarify this please? Thanks :)
>> I always run revdep-rebuild with the -i option. It starts fresh each
>> time or is supposed to anyway. This is a snipped list of what was
>> rebuilt the first time and that it says it wants to rebuild again as I
>> just ran it again:
>>
>> <<< SNIPPED>>>
>> That list is identical to the first time I ran it. I don't know what
>> you were expecting but this is what it does.
>>
>> Dale
>>
>> :-) :-)
>>
>>
> Well, I would expect it to properly recalculate broken packages after
> previous run that failed to complete to build failures
From my understanding, it looks for what packages link/use/whatever the
library then it rebuilds them all. I guess this is one way to catch
them all for sure but it is sort of difficult to know what was already
fixed and what is still broke.
I think I see what you are expecting and I wish it was that way but it
appears we are not getting what we want with this. Is it doable, maybe,
but not at the moment. By the way, I run the unstable versions of those
tools.
I guess if the emerge fails, then one would have to use the --resume
option to try to rebuild packages or just rebuild what fails by hand and
hope you don't miss anything.
Dale
:-) :-)
next prev parent reply other threads:[~2011-10-14 23:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 22:01 [gentoo-dev] rfc: news item for png15 Samuli Suominen
2011-10-14 0:30 ` Peter Volkov
2011-10-14 5:51 ` Michał Górny
2011-10-14 1:59 ` [gentoo-dev] " Ryan Hill
2011-10-15 16:17 ` Samuli Suominen
2011-10-15 21:43 ` Ryan Hill
2011-10-15 21:37 ` Samuli Suominen
2011-10-14 2:48 ` Ryan Hill
2011-10-14 8:46 ` Pacho Ramos
2011-10-14 8:53 ` Dale
2011-10-14 21:03 ` Pacho Ramos
2011-10-14 21:48 ` Dale
2011-10-14 23:20 ` Pacho Ramos
2011-10-14 23:39 ` Dale [this message]
2011-10-21 7:23 ` Paul Varner
2011-10-21 17:46 ` Pacho Ramos
2011-10-14 8:48 ` [gentoo-dev] " Pacho Ramos
2011-10-15 16:35 ` Samuli Suominen
2011-10-15 18:46 ` Pacho Ramos
2011-10-14 23:23 ` Markos Chandras
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=4E98C835.7080606@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-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