From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] 'mad' vs 'mp3' USE flags
Date: Fri, 14 Jul 2006 17:09:03 +0200 [thread overview]
Message-ID: <200607141709.03649@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <1152888235.13861.27.camel@cgianelloni.nuvox.net>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
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 use.mask that i asked WAY before 2.1 release,
but was then left OUT of the freeze and thus of the featureset we can use 6
months from now, I REFUSE to change the behaviour.
You should know better than me this problem, considering that you masked
media-video/transcode on x86 2.4 profile because it was depending on
linux-headers 2.6 (as it should have been) with v4l2 useflag enabled. You
should have use.masked (as it was later done) that useflag as it's 2.6
specific, and I did it that way to satisfy sparc requirement of not having
v4l useflag present for them, as it failed with 2.4 kernel.
So if I didn't do it that way, forcing people wanting v4l support to use v4l
v4l2, now I should still have the stupid, broken, idiotic transcode 0.6 in
the tree, or one of the x86 deptrees broken, or one of the x86 deptrees with
NO v4l at all.
--
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-14 15:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 4:03 [gentoo-dev] 'mad' vs 'mp3' USE flags Daniel Watkins
2006-07-14 14:20 ` Diego 'Flameeyes' Pettenò
2006-07-14 14:43 ` Chris Gianelloni
2006-07-14 14:59 ` Ciaran McCreesh
2006-07-14 17:49 ` [gentoo-dev] " Daniel Watkins
2006-07-14 17:59 ` Ciaran McCreesh
2006-07-14 18:14 ` [gentoo-dev] " Chris Gianelloni
2006-07-14 18:34 ` Ciaran McCreesh
2006-07-14 15:09 ` Diego 'Flameeyes' Pettenò [this message]
2006-07-14 18:20 ` Chris Gianelloni
2006-07-14 18:42 ` Diego 'Flameeyes' Pettenò
2006-07-14 18:45 ` Chris Gianelloni
2006-07-16 4:38 ` Mike Frysinger
2006-07-14 18:24 ` Simon Stelling
2006-07-14 18:43 ` Diego 'Flameeyes' Pettenò
2006-07-14 20:24 ` Zac Medico
2006-07-14 20:31 ` Diego 'Flameeyes' Pettenò
2006-07-15 10:36 ` [gentoo-dev] " Duncan
2006-07-15 15:26 ` Alec Warner
2006-07-14 14:38 ` [gentoo-dev] " Chris Gianelloni
2006-07-14 14:51 ` Diego 'Flameeyes' Pettenò
2006-07-14 16:32 ` Jason Wever
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=200607141709.03649@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@gentoo.org \
--cc=gentoo-dev@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