![](https://seccdn.libravatar.org/avatar/835a9492d596a5f4a8eba92c90ac373b.jpg?s=120&d=mm&r=g)
On Mon, 7 Jun 2021, Jan Engelhardt wrote:
On Monday 2021-06-07 17:15, Ludwig Nussel wrote:
Now with the UsrMerge in place the question arises what to do with all the packages that still install files into /bin, /sbin, /lib and /lib64[...]
[1] list of affected packages: gcc
This will be e.g. "/lib/cpp". You can "fix" it for openSUSE, but chances are upstream may not take a patch to that end, because /lib/cpp is one of those nasty traditional paths that are considered API much more than anything else (quite like /lib/ld-xxx.so.N)
It is/was historically used by X for preprocessing some of its config files. It's not something "upstream" does, btw, it's more like an integration artifact. The gcc package has # Provide the traditional /lib/cpp that only handles C cp $RPM_SOURCE_DIR/cpp $RPM_BUILD_ROOT/lib/ chmod 755 $RPM_BUILD_ROOT/lib/cpp and it's a short script provided by said package: #!/bin/sh # Traditionally, /lib/cpp only knew about C. exec /usr/bin/cpp -xc "$@" moving that to /usr/lib might be possible (it's where it resides after UsrMerge), but then this doesn't make the API any less legacy ... I'll see to "fix" gcc7, but gcc9 should be dropped from Factory as soon as possible instead. Richard. -- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)