public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Martin Holzer" <mholzer@gentoo.org>
To: <gentoo-dev@gentoo.org>
Subject: AW: [gentoo-dev] xine-lib
Date: Fri, 17 Oct 2003 22:37:15 +0200	[thread overview]
Message-ID: <002d01c394ee$748052c0$0801a8c0@svrmarty.gnome.at> (raw)
In-Reply-To: <200310172129.58305.pauldv@gentoo.org>

I've changed SLOT.

This a little bit better


Martin Holzer
sVrmARTY-/irc.freenode.net

Bug-Wrangler, Gentoo Linux
 

-----Ursprüngliche Nachricht-----
Von: Paul de Vrieze [mailto:pauldv@gentoo.org] 
Gesendet: Freitag, 17. Oktober 2003 21:30
An: gentoo-dev@gentoo.org
Betreff: Re: [gentoo-dev] xine-lib


On Friday 17 October 2003 19:20, Patrick Lauer wrote:
>
> 1) How did this slip through QA?
> 2) What is the official policy on breaking emerge -U ? I thought 
> that's a big no-no? 3) Why is a bug that I'd consider a BLOCKER only 
> WONTFIX ?

Unfortunately there are packages that have issues with existing libs. Parts
of 
that are caused by libtool and can often be fixed by the libtool.eclass 
elibtoolize function. I don't know why xine-lib blocks, and I believe that a

fix would be wanted, but in some cases such a thing is the only option.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net


--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2003-10-17 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 17:20 [gentoo-dev] xine-lib Patrick Lauer
2003-10-17 19:05 ` Andrew Gaffney
2003-10-17 19:19   ` C. Brewer
2003-10-18  2:29     ` Andrew Gaffney
2003-10-18 11:02       ` Horror Vacui
2003-10-18 11:33       ` Peter Ruskin
2003-10-17 19:29 ` Paul de Vrieze
2003-10-17 20:37   ` Martin Holzer [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='002d01c394ee$748052c0$0801a8c0@svrmarty.gnome.at' \
    --to=mholzer@gentoo.org \
    --cc=gentoo-dev@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