On 06-May-19 11:02, Goswin von Brederlow wrote: > Andreas Jochens <[EMAIL PROTECTED]> writes: > > Anything which makes it easier to violate this simple policy > > will lead to a mixed usage of /usr/lib and /usr/lib64 and consequently > > to problems which could be difficult to disentangle later. > > The goal would be to actualy get everything into (/usr)/lib64 while > intermittendly allowing a mixed usage. That would allow for FHS > compliance for 32bit libraries shiped in lib32gcc1, lib32stdc++*, > lib32asound, ia32-libs and more to come.
Yes, I understand that it is your goal get everything into /usr/lib64. But this means that every single library package has to be changed to use /usr/lib64 instead /usr/lib. You will probably not achieve that in an etch or even in an etch+1 time frame. You will just get an ugly mixture of /usr/lib and /usr/lib64 usage. If you really want to do this, I suggest that you set up a test archive and convert everything to use /usr/lib64 and collect all the patches that are necessary to achieve this. Then these patches can be reviewed and it can be decided if this is the way to go. However, this has been tried before. The result was that this does not work well. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
