On Friday 14 July 2006 11:09, Diego 'Flameeyes' Pettenò wrote:
> On Friday 14 July 2006 16:43, Chris Gianelloni wrote:
> > While it is a "working" solution, it isn't necessarily a sensible one.
>
> You can take over xine-lib and fix it however you prefer.
>
> As this, as well as any other idea you
On Friday 14 July 2006 22:24, Zac Medico wrote:
> It think we can have it sooner than "another year". There are lots of
> fixes in 2.1.1_pre and I'd like to close the merge window pretty soon so
> that it can be stabilized. I'll work on a patch for package.use and
> package.use.mask so that we sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diego 'Flameeyes' Pettenò wrote:
> Per-package use.mask is not here for another year and in the mean time I
> needed a working solution, this is it.
It think we can have it sooner than "another year". There are lots of fixes in
2.1.1_pre and I'd li
On Fri, 2006-07-14 at 14:20 -0400, Chris Gianelloni wrote:
> On Fri, 2006-07-14 at 17:09 +0200, Diego 'Flameeyes' Pettenò wrote:
> > On Friday 14 July 2006 16:43, Chris Gianelloni wrote:
> > > While it is a "working" solution, it isn't necessarily a sensible one.
> > You can take over xine-lib and
On Friday 14 July 2006 20:24, Simon Stelling wrote:
> In the specific case of xine-lib, the mad USE flag can simply be replaced
> with mp3 because mips, which is the only arch that has the mad USE flag in
> use.mask, doesn't have any version keyworded.
If I revert the change, mips won't be able to
On Friday 14 July 2006 20:20, Chris Gianelloni wrote:
> See, it is this kind of self-serving attitude that really needs to stop
> around here. So the portage devs didn't include something that you
> wanted in the latest release... Did you give them a patch for it?
Do I ask people to give me patche
On Fri, 14 Jul 2006 14:14:39 -0400 Chris Gianelloni
<[EMAIL PROTECTED]> wrote:
| On Fri, 2006-07-14 at 15:59 +0100, Ciaran McCreesh wrote:
| > On Fri, 14 Jul 2006 10:43:54 -0400 Chris Gianelloni
| > <[EMAIL PROTECTED]> wrote:
| > | If the package only uses libmad, and libmad doesn't work on
| > | $
Diego 'Flameeyes' Pettenò wrote:
> On Friday 14 July 2006 06:03, Daniel Watkins wrote:
>> Is there a rationale behind this decision?
> On some systems libmad does not work and has to be masked, if I called it
> mp3,
> it couldn't be use.masked or all the mp3 supports, even when not provided by
>
On Fri, 2006-07-14 at 17:09 +0200, Diego 'Flameeyes' Pettenò wrote:
> On Friday 14 July 2006 16:43, Chris Gianelloni wrote:
> > While it is a "working" solution, it isn't necessarily a sensible one.
> You can take over xine-lib and fix it however you prefer.
Quite honestly, I don't care.
> As thi
On Fri, 2006-07-14 at 15:59 +0100, Ciaran McCreesh wrote:
> On Fri, 14 Jul 2006 10:43:54 -0400 Chris Gianelloni
> <[EMAIL PROTECTED]> wrote:
> | If the package only uses libmad, and libmad doesn't work on $platform,
> | then why not simply disable mp3 support on that platform until libmad
> | is fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 14 Jul 2006, Diego 'Flameeyes' Petten?? wrote:
But as when I asked it was considered "low priority", then you can start
barking at portage devs, instead of me.
I know some of us arch team ninjas asked for this in bug #96368 some time
ago.
On Friday 14 July 2006 16:43, Chris Gianelloni wrote:
> While it is a "working" solution, it isn't necessarily a sensible one.
You can take over xine-lib and fix it however you prefer.
As this, as well as any other idea you can find, is just an HACK until portage
devs implements the per-package u
On Fri, 14 Jul 2006 10:43:54 -0400 Chris Gianelloni
<[EMAIL PROTECTED]> wrote:
| If the package only uses libmad, and libmad doesn't work on $platform,
| then why not simply disable mp3 support on that platform until libmad
| is fixed?
Because it confuses the hell out of users who want to know why
On Friday 14 July 2006 16:38, Chris Gianelloni wrote:
> If a user has USE="mp3 -mad" then they should *always* have working mp3
> support.
Give me per-package use.mask baby, and I'll do whatever you want.
But as when I asked it was considered "low priority", then you can start
barking at portage
On Fri, 2006-07-14 at 16:20 +0200, Diego 'Flameeyes' Pettenò wrote:
> Per-package use.mask is not here for another year and in the mean time I
> needed a working solution, this is it.
While it is a "working" solution, it isn't necessarily a sensible one.
If the package only uses libmad, and libm
On Fri, 2006-07-14 at 05:03 +0100, Daniel Watkins wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> It seems to me that having both of these two flags can only cause confusion.
> I upgraded xine-lib yesterday and spent a very frustrating 2 hours trying
> to work out what had broken my A
On Friday 14 July 2006 06:03, Daniel Watkins wrote:
> Is there a rationale behind this decision?
On some systems libmad does not work and has to be masked, if I called it mp3,
it couldn't be use.masked or all the mp3 supports, even when not provided by
libmad, would have been removed.
Per-packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems to me that having both of these two flags can only cause confusion.
I upgraded xine-lib yesterday and spent a very frustrating 2 hours trying
to work out what had broken my Amarok MP3 playback. It turns out that
having the 'mp3' USE flag set g
18 matches
Mail list logo
