-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go-appimage does NOT follow AppImage spec recommendation nor FHS regarding /usr
prefix
#315
Comments
Thanks @brunvonlope. The files which are not in |
They are coming from the system prefix. They are libraries and some dirs like |
Can you please list the paths of the affected files? Thanks. |
AppDir/lib/arch_triplet have:
AppDir/etc have:
|
Where are these located on your build system? In |
As I said in #315 (comment), they come from the "system prefix" aka |
Thanks. Geneally appimgetool tries to copy files into the AppDir at the same path as they are on the build system, so that the files stay at the same locations relative to each other. |
Yes, Debian have that exact same symlink: /lib pointing to /usr/lib |
The draft spec (https://github.com/AppImage/AppImageSpec/blob/master/draft.md#the-payload-application) says:
However, using go-appimage for deployment makes a .appimage with some deps outside the /usr dir (so in
AppDir
), but others are deployed to inside /usr dir as expected. This inconsistency causes problems:In GIMP .appimage script (due to babl and GEGL and to conform to the best practices of the spec), we force move deps to inside /usr prefix after
-s deploy
: https://gitlab.gnome.org/GNOME/gimp/-/blob/2aaeb55ac0293e8c64b12d82e77dbe14bbfef2ff/build/linux/appimage/2_bundle-gimp-appimage.sh#L299, but this corrupts the RPATH of the deps that we needed to force move.The text was updated successfully, but these errors were encountered: