| 1 |
On Wed, Aug 2, 2017 at 3:07 PM, Martin Vaeth <martin@×××××.de> wrote: |
| 2 |
> Mike Gilbert <floppym@g.o> wrote: |
| 3 |
>> On Wed, Aug 2, 2017 at 1:51 PM, Martin Vaeth <martin@×××××.de> wrote: |
| 4 |
>>> If this already was discussed then sorry for the noise: |
| 5 |
>>> |
| 6 |
>>> What is the rationale for merging lib32 with lib? |
| 7 |
>>> Wouldn't it be somewhat cleaner to have a completely |
| 8 |
>>> split structure |
| 9 |
>>> |
| 10 |
>>> lib64 |
| 11 |
>>> lib32 |
| 12 |
>>> libx32 (possibly) |
| 13 |
>>> lib |
| 14 |
>> |
| 15 |
>> Here are a couple of reasons: |
| 16 |
>> |
| 17 |
>> 1. Other distros (notably Red Hat and Fedora) put 32-bit libs in "lib". |
| 18 |
> |
| 19 |
> According to bug 506276, Debian has instead merged 64-bit to lib. |
| 20 |
> So it seems to me that there is no "mainstream" to follow. |
| 21 |
> Perhaps striving for the cleanest solution would be the best? |
| 22 |
|
| 23 |
Debian puts 64-bit libs in /lib/(host), where (host) is something like |
| 24 |
x86_64-linux-gnu. They don't get put in /lib directly. They call this |
| 25 |
"multiarch". |
| 26 |
|
| 27 |
Migrating Gentoo to a "multiarch" config is a larger project. |
Archives