On 2019-08-17 23:00, Marco d'Itri wrote: > On Aug 17, Aurelien Jarno <aurelien@aurel32.net> wrote: > > > One package should be responsible for providing those links so that > > glibc is not the last package using them. The same way that base-files > > ensure that some directories are present. > usrmerge is only needed to be installed during the conversion of a > non-merged system, so it cannot do this. > > Putting the links inside some package would not solve the problem of > e.g. /lib32/ and /libx32/ being always created even on systems which do > not need them. > And worse, deleting them would become impossible because they would be > created again every time the package is upgraded. > > Doing this in base-files would require having both a "base-files" and > a "base-files-not-merged" package as long as we will keep supporting > non-merged systems, and I think that the complexity of managing this > (in deboostrap and possibly somewhere else) makes this a non-starter. > > If this were implemented in a different package then it would need to be > Essential (and still require special-casing in debootstrap as long as we > will want to support non-merged systems), so I am not sure if this plan > would be accepted by all the stakeholders. Fine it's your opinion. Then I leave you imagine other ideas. I am still believing cluttering the maintainer scripts of the glibc is not the right way to go, even if it's the easy way for you. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
Attachment:
signature.asc
Description: PGP signature