On Thu, 2 Mar 2006 21:29:30 +0100 Grobian <[EMAIL PROTECTED]> wrote:
| On 02-03-2006 20:19:19 +0000, Ciaran McCreesh wrote:
| > On Thu, 2 Mar 2006 21:10:02 +0100 Paul de Vrieze <[EMAIL PROTECTED]>
| > wrote:
| > | I'm also convinced that deliberate circumvention is easy to
| > | detect.
| > 
| > In that case, please provide a list of cases where !arch? flags are
| > being used to circumvent repoman warnings, where the correct
| > solution
| 
| Circumvent?  Can you elaborate on that?  repoman does have a problem
| with this, while portage does not.

Okay. This is a rather hypothetical example, since alsa is masked on
relevant profiles, but it's a nice, easy to understand case that's on a
worryingly common theme.

Say you create a new package, which we'll call mysoundthing. You add
mysoundthing 1.1 to the tree, and it picks up a ~sparc keyword. Along
comes mysoundthing 1.2, complete with optional ALSA support. You add in
a dep of alsa? ( whatever the alsa libraries are these days ), and try
to commit it. Repoman complains that the alsa libraries are unkeyworded
on sparc.

Now, you've heard that dropping keywords is bad. But you have a clever
idea, and make the dep alsa? ( !sparc? ( alsa libraries ) ). This gets
past repoman just fine.

Along comes 2006 (or late 2005), and some sparc profiles get working
ALSA support. So, the ALSA libraries are keyworded / profile masked as
appropriate. Along comes joeuser, who installs mysoundthing. He wants
ALSA support, so he turns on the alsa USE flag. Sure enough, emerge -pv
indicates that ALSA will be enabled.

However... Because of the nasty !arch? hack, he won't get alsa support
until the arch team goes through and fixes this ebuild (and probably
several others too...).

The correct solution is to get the alsa USE flag use.masked on various
profiles (as, in the alsa case, it is). However, there are a whooole
load of ebuilds in the tree that don't do this properly.

Scary sidenote: a similar hack has lead to some forums users suggesting
that the way to avoid getting mozilla as part of gnome was to use
USE="mips".

This issue has been a major pain in the ass for some of the arch teams,
and it will very likely be another major pain in the ass in the future,
again and again.

-- 
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm

Attachment: signature.asc
Description: PGP signature

Reply via email to