Dnia 2014-04-01, o godz. 00:16:17
Michał Górny <[email protected]> napisał(a):

> Your thoughts?

Following the feedback on the mailing list, IRC and bugzilla, and some
of my own thoughts, I'd like to put a few important extra points I've
missed in the original mail:

1. playing with the masks will cause a large unnecessary --changed-use
rebuild for stable users, including the users of no-multilib profiles,

2. prebuilt software ebuilds are allowed to unconditionally use abi_*
flags in USE dependencies. Masking the native flags would break those
dependencies.

For those unaware, 2. here means that a pre-built x86 software can use
a single dependency like:

  dev-libs/libfoo[abi_x86_32]

that would satisfy both x86 (since abi_x86_32 is use.forced) and amd64
(by pulling in multilib).

Considering the two points above, I'd like to withdraw the idea of
adding global masks for abi_* and just leave it amd64-specific.


Additionally, the following important points were raised:

1. ulm believes that the use.force implicit IUSE magic is a bug in
portage and oughtn't be trusted upon,

2. keeping extra package.use.stable.masks for different arches seems
pretty much unmaintainable. It would mean a lot of duplicate package
lists in different profiles that need to be kept in sync.

Instead, I'd like to limit the scope of stable masks necessity and just
focus on stabilizing packages properly.


That is, the new position is:

1. we keep the flags for packages that are in emul-linux stable-masked
on amd64 until we decide to replace emul-linux,

2. we stabilize package dependencies properly so that there are no
dependency tree breakage when new ABIs are added.

Rationale: the multilib conversions are no longer moving in the fast
pace they used to, and the stabilization interest conflicts are less
likely than they were at the time of introducing
package.use.stable.masks.

Especially now that new multilib conversions are made package.masked,
we can give them enough time for people to be ready to stabilize
in some sane way.

We'd like to still keep the emul-linux-replacing packages masked
in order to keep emul-linux as single multilib provider for stable
packages. This is in order to avoid exposing stable users to issues
involved with partial conversions, and to confusing --autounmask
behavior that can possibly be created through mixing emul-linux
and multilib packages.


If nobody minds, I'm doing a repoman run now and in a few hours I
should have a list of packages that need to be stabilized in order to
clean up the dependency trees for multilib packages.

-- 
Best regards,
Michał Górny

Attachment: signature.asc
Description: PGP signature

Reply via email to