gsocket: DSO files are distributed wrongly in bin dir used for executables
gs_so and gs_uchroot_so are not executables but in fact DSO libs. They should be distributed in the matching FHS directories like /usr/lib instead of putting them in the bin directory.
This would be welcoming for distro folks 🐱
Edit: I believe it would also make sense to move pure helper scripts as gs_funcs to the same place. Either the location can be probed or some of the scripts should be converted to .in files that autotools substitutes with configured libdir etc.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (12 by maintainers)
@SkyperTHC urgh, I actually forgot to put it into the repo and just used my local one 😹 I will handle this most likely today evening.
@UnlimitedCookies https://archlinux.org/packages/community/x86_64/gsocket/
This has now been release in 1.4.28 (and master branch).
I will change it for the next deb files old man.
Yes, distro packaging requires to only dist executables in the bin directories, such libs must be put somewhere else like
/usr/ib. I’ve seen code in the shell scripts that already probe for certain directories, can’t that be used in a similar way? the probe can check for all valid FHS compliant directories, those include/usr/localetc? If you think you don’t want to solve this, I will need to provide downstream patches but I don’t think that’s a good approach and we try to cooperate as a distro policy with upstream instead of going nuts with downstream patches.Maybe a middle way would be a configure switch like
--fhsor similar just changes the way where which part of the toolchain is distributed. The probe function can then just prefere to search in the same directory as the binary to preserve the status quo and if its not found it continues to probe the FHS directories. This would imo solve all cases without the need to have .in shell scripts.