[gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[Thomas Sachau]

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

Hi together,

as announced in a previous mail, i created a fork of portage, which has support to create 32bit libs
during compile phase for 64bit platforms (currently amd64 tested, ppc64 untested).

In short, it does execute every src_* phase twice with keeping a workdir for every ABI and saving
some default environment vars (like *FLAGS). Since the current ABI is the last one in this order,
the 64bit phase will overwrite everthing from 32bit phase except those parts, which have a different
install location, so mostly libs, which go in lib32 instead of lib64.

A current ebuild and docs for using it are currently in the portage-multilib branch of the multilib
overlay.

I asked zmedico about inclusion into the main svn tree of portage, but he requested a council ok
before he would be accepting it. So this is my request for discussion and ok (in tomorrows or the
following meeting) from the council.


-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

Thomas Sachau wrote:
> Hi together,
> 
> as announced in a previous mail, i created a fork of portage, which has support to create 32bit libs
> during compile phase for 64bit platforms (currently amd64 tested, ppc64 untested).
> 
> In short, it does execute every src_* phase twice with keeping a workdir for every ABI and saving
> some default environment vars (like *FLAGS). Since the current ABI is the last one in this order,
> the 64bit phase will overwrite everthing from 32bit phase except those parts, which have a different
> install location, so mostly libs, which go in lib32 instead of lib64.
> 
> A current ebuild and docs for using it are currently in the portage-multilib branch of the multilib
> overlay.
> 
> I asked zmedico about inclusion into the main svn tree of portage, but he requested a council ok
> before he would be accepting it. So this is my request for discussion and ok (in tomorrows or the
> following meeting) from the council.
> 
> 

I won't have enough time to investigate this before the meeting tomorrow
so I won't be putting up a vote for it on the agenda. We can discuss it
during the open floor if there's time.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[Zac Medico]

Thomas Sachau wrote:
> Hi together,
> 
> as announced in a previous mail, i created a fork of portage, which has support to create 32bit libs
> during compile phase for 64bit platforms (currently amd64 tested, ppc64 untested).
> 
> In short, it does execute every src_* phase twice with keeping a workdir for every ABI and saving
> some default environment vars (like *FLAGS). Since the current ABI is the last one in this order,
> the 64bit phase will overwrite everthing from 32bit phase except those parts, which have a different
> install location, so mostly libs, which go in lib32 instead of lib64.
> 
> A current ebuild and docs for using it are currently in the portage-multilib branch of the multilib
> overlay.
> 
> I asked zmedico about inclusion into the main svn tree of portage, but he requested a council ok
> before he would be accepting it. So this is my request for discussion and ok (in tomorrows or the
> following meeting) from the council.

An important thing to note is that there are necessary changes to
emul-* ebuilds that are technically an EAPI change, since they won't
work with old package managers that don't have support for lib32 USE
 flags.
-- 
Thanks,
Zac

Re: [gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[Thomas Sachau]

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

Zac Medico schrieb:
> Thomas Sachau wrote:
>> Hi together,
>>
>> as announced in a previous mail, i created a fork of portage, which has support to create 32bit libs
>> during compile phase for 64bit platforms (currently amd64 tested, ppc64 untested).
>>
>> In short, it does execute every src_* phase twice with keeping a workdir for every ABI and saving
>> some default environment vars (like *FLAGS). Since the current ABI is the last one in this order,
>> the 64bit phase will overwrite everthing from 32bit phase except those parts, which have a different
>> install location, so mostly libs, which go in lib32 instead of lib64.
>>
>> A current ebuild and docs for using it are currently in the portage-multilib branch of the multilib
>> overlay.
>>
>> I asked zmedico about inclusion into the main svn tree of portage, but he requested a council ok
>> before he would be accepting it. So this is my request for discussion and ok (in tomorrows or the
>> following meeting) from the council.
> 
> An important thing to note is that there are necessary changes to
> emul-* ebuilds that are technically an EAPI change, since they won't
> work with old package managers that don't have support for lib32 USE
>  flags.

I currently have emul-* ebuilds in my branch, which use lib32 usedeps, but ebuilds could instead
just use something like "|| ( emul-linux-qtlibs qt-core[lib32] )". So this part should be no
drawback for actually adding multilib support to main tree portage.

-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 1421 bytes --]

On Sunday 11 October 2009 06:21:14 Thomas Sachau wrote:
> as announced in a previous mail, i created a fork of portage, which has
>  support to create 32bit libs during compile phase for 64bit platforms
>  (currently amd64 tested, ppc64 untested).
> 
> In short, it does execute every src_* phase twice with keeping a workdir
>  for every ABI and saving some default environment vars (like *FLAGS).
>  Since the current ABI is the last one in this order, the 64bit phase will
>  overwrite everthing from 32bit phase except those parts, which have a
>  different install location, so mostly libs, which go in lib32 instead of
>  lib64.
> 
> A current ebuild and docs for using it are currently in the
>  portage-multilib branch of the multilib overlay.

your git instructions are overly complicated (doc/portage-multilib-
instructions).  your two checkouts and .git/config edit are one command:
git checkout -b portage-multilib origin/portage-multilib

you really should line wrap that file too

> I asked zmedico about inclusion into the main svn tree of portage, but he
>  requested a council ok before he would be accepting it. So this is my
>  request for discussion and ok (in tomorrows or the following meeting) from
>  the council.

getting review + approval in a day or two is pretty unreasonable, especially 
when info as to what is being changed/proposed isnt well documented.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] Moving real multilib support into main tree portage with request for council decision

[Thomas Sachau]

[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]

Mike Frysinger schrieb:
> On Sunday 11 October 2009 06:21:14 Thomas Sachau wrote:
>> as announced in a previous mail, i created a fork of portage, which has
>>  support to create 32bit libs during compile phase for 64bit platforms
>>  (currently amd64 tested, ppc64 untested).
>>
>> In short, it does execute every src_* phase twice with keeping a workdir
>>  for every ABI and saving some default environment vars (like *FLAGS).
>>  Since the current ABI is the last one in this order, the 64bit phase will
>>  overwrite everthing from 32bit phase except those parts, which have a
>>  different install location, so mostly libs, which go in lib32 instead of
>>  lib64.
>>
>> A current ebuild and docs for using it are currently in the
>>  portage-multilib branch of the multilib overlay.
> 
> your git instructions are overly complicated (doc/portage-multilib-
> instructions).  your two checkouts and .git/config edit are one command:
> git checkout -b portage-multilib origin/portage-multilib
> 
> you really should line wrap that file too
> 

both changed

>> I asked zmedico about inclusion into the main svn tree of portage, but he
>>  requested a council ok before he would be accepting it. So this is my
>>  request for discussion and ok (in tomorrows or the following meeting) from
>>  the council.
> 
> getting review + approval in a day or two is pretty unreasonable, especially 
> when info as to what is being changed/proposed isnt well documented.
> -mike

Thats why my intention was to get it on todays agenda for discussion (and more people looking at it)
and possible decision at the following meeting, so the wording may have been unclear.

-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]