From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Eclass assisted multilib dependent cache updates
Date: Mon, 4 Jan 2016 16:45:32 +0100 [thread overview]
Message-ID: <20160104164532.4f52654a@gentoo.org> (raw)
In-Reply-To: <1451750071.31635.9.camel@gentoo.org>
On Sat, 02 Jan 2016 16:54:31 +0100
Gilles Dartiguelongue <eva@gentoo.org> wrote:
> Hello all,
>
> while working on bug #518422, I found out that while eclass calls the
> relevant cache updates it has no idea whether or not it is called in a
> multilib context or not.
Hmm... what's the problem here ?
What you seem to call "not a multilib context" is a multilib build with
only one ABI. That's one of the points of inheriting the
multilib eclasses.
> Imho, this leads to avoidable human errors where one thinks eclass
> will take care of lib dependent caches, which it does, but not for all
> enabled ABIs which could lead to reduced functionality for non-native
> ABIs.
>
> While it seems reasonable to call multilib_foreach_abi
> gnome2_pkg_postinst for multilib enabled ebuilds, it is still not
> ideal as it will call a lot of functions for no good reason. On the
> other hand, checking environment variable set by multilib eclasses
> does not seem like a robust solution.
>
> Is there any reasonable way to make phase functions aware of if they
> are running in a multilib enabled ebuild to adjust their behavior ?
Per the above, 'multilib_foreach_abi' seems just fine. Is there a real
problem with it?
next prev parent reply other threads:[~2016-01-04 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 15:54 [gentoo-dev] Eclass assisted multilib dependent cache updates Gilles Dartiguelongue
2016-01-04 15:45 ` Alexis Ballier [this message]
2016-01-04 16:29 ` Ian Stakenvicius
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=20160104164532.4f52654a@gentoo.org \
--to=aballier@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