public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Updating libpng: another lib tool cockup?
Date: Mon, 19 Sep 2011 10:49:53 -0500	[thread overview]
Message-ID: <CAEH5T2OwADURCB1PGdNz4yeUhA0F1uSA5N_neBQhFjhFXPCFfA@mail.gmail.com> (raw)
In-Reply-To: <yu9vcsowpcj.fsf_-_@nyu.edu>

On Mon, Sep 19, 2011 at 9:58 AM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> OK.  But the claim was that: if
>   revdep-rebuild
> with no argument found nothing to build, then
>   revdep-rebuild --library <some-library>
> will find nothing.

I think what everyone (except Michael S) seems to be confused about is:

Normal revdep-rebuild (with no options) looks for broken shared
library dependencies and rebuilds them. If you run it again, it won't
rebuild anything, because the dependency has been fixed.

Using the --library switch, however, it looks for everything built
against that library, regardless of whether or not the dependency is
broken, and rebuilds it. If you run this command 10 times in a row
it'll rebuild the same libraries 10 times.

Presumably, there are cases (like libpng) when it is desirable to
rebuild dependencies but they aren't "broken" in the way that
revdep-rebuild normally can detect. So using --library will
brute-force rebuild everything that depends on that library, just to
make sure they are built against the new version.

Moral of the story; if an ebuild tells you to revdep-rebuild
--library, do it. :)



  parent reply	other threads:[~2011-09-19 15:53 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 20:10 [gentoo-user] Updating libpng: another libtool cockup? walt
2011-09-18 20:48 ` Michael Mol
2011-09-18 20:57 ` Thanasis
2011-09-18 21:54   ` Mick
2011-09-18 21:58 ` Allan Gottlieb
2011-09-18 23:39   ` Alan McKinnon
2011-09-19 10:06     ` [gentoo-user] " walt
2011-09-19 14:10       ` Alan McKinnon
2011-09-19 14:20         ` Allan Gottlieb
2011-09-19 14:34           ` Michael Schreckenbauer
2011-09-19 14:58             ` [gentoo-user] Re: Updating libpng: another lib tool cockup? Allan Gottlieb
2011-09-19 15:19               ` Michael Schreckenbauer
2011-09-19 15:28               ` Alan McKinnon
2011-09-19 15:49                 ` Michael Schreckenbauer
2011-09-19 15:49               ` Paul Hartman [this message]
2011-09-19 17:57                 ` Allan Gottlieb
2011-09-19 18:19                   ` Paul Hartman
2011-09-19 20:08                     ` Allan Gottlieb
2011-09-20 10:38                   ` Neil Bothwick
2011-09-20 12:57                     ` Allan Gottlieb
2011-09-19 16:30               ` covici
2011-09-19 14:36           ` [gentoo-user] Re: Updating libpng: another libtool cockup? Michael Mol
2011-09-19 20:33             ` Mark Knecht
2011-09-19 20:41               ` Michael Mol
2011-09-19 20:52                 ` Mark Knecht
2011-09-19 21:10                   ` Michael Schreckenbauer
2011-09-19 21:28                     ` Mark Knecht
2011-09-19 15:07         ` walt
2011-09-19 15:49         ` David W Noon
2011-09-19 20:54           ` Peter Humphrey
2011-09-19 22:29             ` covici
2011-09-20 10:41               ` Neil Bothwick
2011-09-19 14:06     ` [gentoo-user] " Allan Gottlieb
2011-09-19 21:04 ` [gentoo-user] " Nikos Chantziaras

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=CAEH5T2OwADURCB1PGdNz4yeUhA0F1uSA5N_neBQhFjhFXPCFfA@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@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