| 1 |
El sáb, 22-09-2012 a las 23:24 +0200, Michał Górny escribió: |
| 2 |
> It is a simple eclass using autotools out-of-source builds to build |
| 3 |
> packages for multiple ABIs when multilib is supported. |
| 4 |
> |
| 5 |
> Use case: xorg packages, ask Matt. |
| 6 |
> --- |
| 7 |
> gx86/eclass/autotools-multilib.eclass | 72 +++++++++++++++++++++++++++++++++++ |
| 8 |
> 1 file changed, 72 insertions(+) |
| 9 |
> create mode 100644 gx86/eclass/autotools-multilib.eclass |
| 10 |
> |
| 11 |
> diff --git a/gx86/eclass/autotools-multilib.eclass b/gx86/eclass/autotools-multilib.eclass |
| 12 |
> new file mode 100644 |
| 13 |
> index 0000000..1a345a1 |
| 14 |
> --- /dev/null |
| 15 |
> +++ b/gx86/eclass/autotools-multilib.eclass |
| 16 |
> @@ -0,0 +1,72 @@ |
| 17 |
> +# Copyright 1999-2012 Gentoo Foundation |
| 18 |
> +# Distributed under the terms of the GNU General Public License v2 |
| 19 |
> +# $Header: $ |
| 20 |
> + |
| 21 |
> +# @ECLASS: autotools-multilib.eclass |
| 22 |
> +# @MAINTAINER: |
| 23 |
> +# Michał Górny <mgorny@g.o> |
| 24 |
> +# @BLURB: autotools-utils wrapper for multilib builds |
| 25 |
> +# @DESCRIPTION: |
| 26 |
> +# The autotools-multilib.eclass is an autotools-utils.eclass(5) wrapper |
| 27 |
> +# introducing support for building for more than one ABI (multilib). |
| 28 |
> +# |
| 29 |
> +# Inheriting this eclass sets IUSE=multilib and exports autotools-utils |
| 30 |
> +# phase function wrappers which build the package for each supported ABI |
| 31 |
> +# if the flag is enabled. Otherwise, it works like regular |
| 32 |
> +# autotools-utils. |
| 33 |
[...] |
| 34 |
|
| 35 |
One problem that I remembered now: |
| 36 |
If every ebuild inheritting this eclass (either this one or similar) |
| 37 |
will add a "multilib" USE, people running multilib profiles will get it |
| 38 |
enabled for ALL packages inheritting it, causing them to see how their |
| 39 |
systems grow a lot because they will have 32bits libs for all packages, |
| 40 |
even when not needed. For example, in my systems I need gtk+ 32 bits |
| 41 |
libs, but not qt ones as I don't have any qt based app requiring 32bits |
| 42 |
installed. |
| 43 |
|
| 44 |
Maybe the way to workaround this would be to rename it to something like |
| 45 |
"32bits", that way if, for example, acroread RDEPENDs on gtk+[32bits], |
| 46 |
it would only be enabled for needed packages not all |
Archives