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
Hard-coded libexec in setup.py #3597
Comments
This used to be per-distro but now that Debian has finally caught up with the filesystem spec, this is no longer the case: f9108f5 |
Understood, I recall notifications from gh about libexec around that time frame. I certainly wouldn't advocate for changing the default, just having a way to tie-in to the macro which TW defines as if is_openSUSE():
# basically need $(basename $(rpm -E '%{_libexecdir}'))
libexec_dir = "__LIBEXECDIR__"
else
libexec_dir = "libexec"
...
add_data_files(libexec_dir + "/xpra/", ["fs/libexec/xpra/%s" % x for x in libexec_scripts]) So the same sed that fixes up Currently, the |
Applied this ugly fix in the commit above. Do you happen to know when opensuse is going to catch up with |
Thanks :) I'll keep an eye on it ~ not sure what Leap's future holds (since it's tied to SLE, and may even pivot in a different direction in a release or two). Seems $ sudo chroot /var/tmp/build-root/openSUSE_Tumbleweed-x86_64
:/ # cd /usr/lib/rpm
:/usr/lib/rpm # grep _libexecdir ./platform/x86_64-linux/macros
%_libexecdir %{_exec_prefix}/libexec
$ sudo chroot /var/tmp/build-root/15.4-x86_64/
:/ # cd /usr/lib/rpm/
:/usr/lib/rpm # grep _libexecdir ./platform/x86_64-linux/macros
%_libexecdir %{_exec_prefix}/lib |
I really appreciate you making this change ; I was able to use a03b3f6 and make Thanks! |
For openSUSE Leap 15.4 (latest Leap),
%{_libexecdir}
resolves to/usr/lib
(vs./usr/libexec
for TW):Would it be possible to have something that ties into
is_openSUSE()
so the distro-specific value can be swapped in? a la__FILLUPDIR__
&__UNITDIR__
The issue presents itself in https://github.com/Xpra-org/xpra/blob/master/setup.py#L1592
The text was updated successfully, but these errors were encountered: