В письме от 29 апреля 2013 15:43:03 пользователь Jeroen Roovers написал:
> On Mon, 29 Apr 2013 16:14:51 +0900
>
> heroxbd wrote:
> > KEYWORDS="~hppa-hpux ~m68k-mint ~ppc-aix ~x64-solaris ~x86-interix["]
> >
> > KEYWORDS_ARCH="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64
> > ~s390 ~sh ~
On Mon, 29 Apr 2013 16:14:51 +0900
heroxbd wrote:
> KEYWORDS="~hppa-hpux ~m68k-mint ~ppc-aix ~x64-solaris ~x86-interix["]
>
> KEYWORDS_ARCH="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64
> ~s390 ~sh ~sparc ~x86"
Regardless of your chance of success in making the extra complexity
manage
Hi Ben,
Ben de Groot writes:
> To me this looks to be needlessly complex.
There is an alternative way to do this:
@-linux
to mean "the ebuild works on every keyworded arch on Prefix with Linux
kernel".
Cheers,
Benda
Dearr Fabian,
Fabian Groffen writes:
>> Furthermore if the ebuild has "amd64" keyword, it will certainly
>> build on amd64-linux too.
>
> Somewhat likely, but absolutely not true.
Sorry, the original phrase was vague. I meant, if an ebuild is keyworded
"amd64" and "x86-linux", it will certainly
On 29 April 2013 15:14, heroxbd wrote:
>
> Dear all,
>
> In GLEP22[1], reasonable defaults has been introduced to prevent the
> explosion of keywords. With the growth of Gentoo Prefix, however, a
> substantial amount of keywords are introduced. Among them, duplex
> information exists. For example,
Hi,
On 29-04-2013 16:14:51 +0900, heroxbd wrote:
> In GLEP22[1], reasonable defaults has been introduced to prevent the
> explosion of keywords. With the growth of Gentoo Prefix, however, a
> substantial amount of keywords are introduced. Among them, duplex
> information exists. For example, an eb
Dear all,
In GLEP22[1], reasonable defaults has been introduced to prevent the
explosion of keywords. With the growth of Gentoo Prefix, however, a
substantial amount of keywords are introduced. Among them, duplex
information exists. For example, an ebuild keyworded x86-linux(Gentoo
Prefix on x86 l
