From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: multilib@gentoo.org
Subject: Re: [gentoo-dev] Stable masks on multilib packages
Date: Tue, 01 Apr 2014 09:58:37 -0400 [thread overview]
Message-ID: <1396360717.20406.12.camel@rook> (raw)
In-Reply-To: <CAB9SyzRXkymQHae=QysHhBAbCs+MMSqir9QOGc8YQ35gJQfQ5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
On Tue, 2014-04-01 at 13:13 +0800, Ben de Groot wrote:
> On 1 April 2014 06:16, Michał Górny <mgorny@gentoo.org> wrote:
> > Hello, all.
> >
> > The late multilib ppc issues made me re-check our stable masks on
> > abi_x86_* flags and, honestly, I'm not sure if we're doing things
> > the right way.
> >
> > That said, I have an alternate idea inspired by the ppc breakage.
> >
> > Your thoughts?
>
> In my opinion your multilib approach introduces an unnecessary degree
> of complexity, which --as has been shown here again-- is prone to
> breakage.
>
> It would be best for our beloved distro to revert all the multilib
> changes, and try a different approach, or leave this prone-to-breakage
> implementation to an overlay for the few people who would actually
> benefit from it.
Speaking as a wine maintainer, the emul-linux-x86-* approach has many
times been proven to be an embarrassing failure and the main source of
pain and frustration for wine users. The sooner emul-linux-x86-* can be
removed from the tree, the better for Gentoo.
I am aware of only two solutions to the emul-linux-x86-* problems :
multilib-portage and multilib-build.eclass. The first requires everybody
to switch to a new package manager. The second allows us to keep using
portage, but requires library maintainers to add some simple boilerplate
to their ebuilds for multilib support.
Do you have yet another alternative in mind?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-01 13:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 22:16 [gentoo-dev] Stable masks on multilib packages Michał Górny
2014-03-31 23:09 ` Anthony G. Basile
2014-04-01 5:54 ` Michał Górny
2014-04-01 11:26 ` [gentoo-dev] " Duncan
2014-04-01 15:49 ` Ian Stakenvicius
2014-04-01 15:55 ` Michał Górny
2014-04-01 11:40 ` [gentoo-dev] " Anthony G. Basile
2014-04-01 12:04 ` Anthony G. Basile
2014-04-01 5:13 ` Ben de Groot
2014-04-01 13:58 ` Alexandre Rostovtsev [this message]
2014-04-01 14:43 ` Rich Freeman
2014-04-02 0:13 ` Patrick Lauer
2014-04-02 0:58 ` Rich Freeman
2014-04-02 17:42 ` Ciaran McCreesh
2014-04-02 9:14 ` Ben de Groot
2014-04-02 13:07 ` Mike Frysinger
2014-04-02 13:43 ` Alexandre Rostovtsev
2014-04-01 23:38 ` Patrick Lauer
2014-04-02 9:25 ` Ben de Groot
2014-04-02 13:55 ` Alexandre Rostovtsev
2014-04-02 20:52 ` Matt Turner
2014-04-01 15:12 ` Ian Stakenvicius
2014-04-01 15:32 ` Michał Górny
2014-04-01 17:15 ` Michał Górny
2014-04-02 8:12 ` [gentoo-dev] " Duncan
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=1396360717.20406.12.camel@rook \
--to=tetromino@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=multilib@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