1 |
On Sat, 10 Oct 2015 17:48:15 -0500 |
2 |
William Hubbs <williamh@g.o> wrote: |
3 |
|
4 |
> All, |
5 |
> |
6 |
> fhs 3.0 was approved in June this year [1] [2]. |
7 |
> |
8 |
> The piece of it that I want to bring up is the lib and libxx |
9 |
> directories, both in / and /usr. The way I read the fhs, /lib and |
10 |
> /usr/lib should hold the files for the default abi and /libxx and |
11 |
> /usr/libxx should hold the files for the alternate abis. In earlier |
12 |
> fhs, there was an exception for amd64 which stated that the default |
13 |
> libraries should be in /lib64 and /usr/lib64. However, that exception |
14 |
> is now gone. |
15 |
> |
16 |
> I know there was discussion/work in the past on removing the |
17 |
> lib->lib64 symlinks on amd64, but I don't remember what happened to |
18 |
> that discussion. So, I would like to bring it up again and get the |
19 |
> info. |
20 |
> |
21 |
> What would it take for us to remove the lib->lib64 links? |
22 |
> |
23 |
> What would it take for us to do this migration on live systems? |
24 |
|
25 |
I did this for amd64-fbsd, close to its beginning in gentoo; it's a |
26 |
pain for users: it basically sums up to 'set SYMLINK_LIB=no, rm |
27 |
lib, mv lib64 lib, ln -s lib lib64, emerge -e world, rm lib64' |
28 |
( see |
29 |
https://wiki.gentoo.org/wiki/Gentoo_FreeBSD#All_commands_is_not_working_after_emerge_sys-apps.2Fbaselayout |
30 |
) |
31 |
|
32 |
emerge -e world was there to kill every hardcoded lib64 in binaries |
33 |
|
34 |
vapier has been working on this afaik |
35 |
( https://bugs.gentoo.org/show_bug.cgi?id=506276 ), so maybe there is a |
36 |
better solution, but since this changes econf args and get_libdir |
37 |
ouput, I'm not sure 'emerge -e world' can be avoided... |
38 |
|
39 |
|
40 |
Alexis. |