public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Playsound . . . won't!
Date: Mon, 17 Sep 2007 15:33:54 +0100	[thread overview]
Message-ID: <200709171534.04634.michaelkintzios@gmail.com> (raw)
In-Reply-To: <200709171402.02484.mike@gaima.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

On Monday 17 September 2007, Mike Williams wrote:
> On Monday 17 September 2007 13:41:37 Alan McKinnon wrote:
> > More like revdep-rebuild doesn't know how to build libOffFLAC anymore as
> > the ebuild that put it there isn't in portage anymore or masked or
> > keyworded or whatevered. I've seen this myself a time or three on my
> > own machines.
> >
> > There's nothing revdep-rebuild can do about this except shrug and leave
> > it alone, but the output could be more informative. Perhaps a feature
> > request in is order here
>
> revdep-rebuild doesn't work like that.
> If a binary is dynamically linked to a library that doesn't exist anymore,
> the package owning the binary is rebuilt, as portage is unlikely to know
> what package supplied a file that doesn't exist. The idea being the package
> will find and link against libraries that do exist.
>
> In this case it would seem that revdep-rebuild should be trying to emerge:
> media-libs/sdl-sound
> media-plugins/gst-plugins-flac
> media-plugins/gst-plugins-oss
> media-libs/akode

This is how I understood that is should work too.  If for what ever reason it 
doesn't rebuild the above packages itself, it should either say why (e.g. 
keyword masked, Blocked, not in portage, etc.) and, or pass it on to me to 
emerge/unmerge manually as required.  I thought that invariably this is how 
portage behave, hence this thread to resolve my confusion.  Are we in 
agreement that there is something wrong on this occasion - should I file a 
bug?  Or a 'feature request?  Or wait until it happens again?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-09-17 14:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 22:11 [gentoo-user] Playsound . . . won't! Mick
2007-09-15 22:21 ` Bo Ørsted Andresen
2007-09-15 22:22 ` Danilo Marcelo
2007-09-15 22:34 ` Alan McKinnon
2007-09-17 10:29   ` Mick
2007-09-17 10:41     ` Neil Bothwick
2007-09-17 10:59       ` Mick
2007-09-17 13:00         ` Alan McKinnon
2007-09-18 17:50           ` Mick
2007-09-18 20:50             ` Neil Bothwick
2007-09-17 13:51         ` [gentoo-user] " Anno v. Heimburg
2007-09-17 14:43           ` Mick
2007-09-17 11:11     ` [gentoo-user] " Graham Murray
2007-09-17 12:41       ` Alan McKinnon
2007-09-17 13:02         ` Mike Williams
2007-09-17 14:33           ` Mick [this message]
2007-09-17 16:20             ` Mike Williams
2007-09-17 17:27               ` Mick
2007-09-17 20:17                 ` Paul Varner
2007-09-17 18:53         ` Bo Ørsted Andresen
2007-09-17 18:49     ` Bo Ørsted Andresen
2007-09-17 21:05       ` Mick
2007-09-17 21:26         ` Bo Ørsted Andresen

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=200709171534.04634.michaelkintzios@gmail.com \
    --to=michaelkintzios@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