public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Updating libpng: another libtool cockup?
Date: Mon, 19 Sep 2011 16:41:47 -0400	[thread overview]
Message-ID: <CA+czFiBhzjzk7ZHembe0KDpH+fCOj_z-CM9wW2BFYEqtwwDfiA@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+efhTU0My3QpQDmPdMs6Aj62HAbbWoU9dCZvAfnFW8CDuA@mail.gmail.com>

On Mon, Sep 19, 2011 at 4:33 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Mon, Sep 19, 2011 at 7:36 AM, Michael Mol <mikemol@gmail.com> wrote:
>> On Mon, Sep 19, 2011 at 10:20 AM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> <SNIP>
>>> ajglap gottlieb # revdep-rebuild; revdep-rebuild --library '/usr/lib64/libpng14.so.14'
> <SNIP>
>>
>> Is there no automated way to catch these? --library expects an
>> argument; how do I know which libraries to feed it?
>
> My question exactly. It's not likeyou can look at just names of
> libraries as I think to do this right you've got to look at every
> revision of every library on the system, don't you?
>
> It's possible that this problem could exist for a long while if a
> program doesn't get used much...

Based on subsequent discussion since I wrote that question, I think
the answer is, "currently, no." Ebuillds would need more metadata, and
portage would need to be more aware of deep dependencies.

I'm not sure of revdep-rebuild's angle, or how it might be able to be
improved to detect errors that don't come from broken linkage.
-- 
:wq



  reply	other threads:[~2011-09-19 20:43 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
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 [this message]
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=CA+czFiBhzjzk7ZHembe0KDpH+fCOj_z-CM9wW2BFYEqtwwDfiA@mail.gmail.com \
    --to=mikemol@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