| 1 |
Hi folks, |
| 2 |
|
| 3 |
|
| 4 |
i would like to hear about other opinions about real multilib support within our tree and package |
| 5 |
managers. From what i know, there are mainly 2 different ideas: |
| 6 |
|
| 7 |
1. Do the main stuff in the package manager (e.g. if the ARCH is amd64 and the package has x86 |
| 8 |
keyword, the package manager adds a lib32 useflag, which would additionally install the 32bit |
| 9 |
variant of that package together with the normal 64bit install). |
| 10 |
|
| 11 |
pro: -much lesser work for package maintainers |
| 12 |
|
| 13 |
contra: -needs addition in PMS and support in the pms, which will need some work on their side |
| 14 |
|
| 15 |
2. Do the main stuff in the ebuilds themselves (e.g. an additional eclass multilib-native.eclass, |
| 16 |
any ebuild with 32bit support would then need adaption and of course inheriting that eclass) |
| 17 |
|
| 18 |
For reference, there are some users in #gentoo-multilib-overlay, which try to implement this option |
| 19 |
in an git based overlay. |
| 20 |
|
| 21 |
the arguments are more or less the reverse of above: |
| 22 |
|
| 23 |
pro: -no need for PMS/PM support |
| 24 |
-could be started and improved at any time |
| 25 |
|
| 26 |
contra: -needs much additional work since many ebuilds need to be changed and adapted |
| 27 |
|
| 28 |
|
| 29 |
Which option do you prefer? Or does anyone have another option? Which additional arguments are there |
| 30 |
for those options? |
| 31 |
|
| 32 |
-- |
| 33 |
Thomas Sachau |
| 34 |
|
| 35 |
Gentoo Linux Developer |
Archives