You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/usr/bin: Non-essential command binaries (not needed in single-user mode); for all users.
This was noticed because we have tooling in archlinux that scans through the binaries and notifies us when there are rebuilds needed (i.e. in this case for a protobuf update) where hyperion was missed because it has its binaries in this non-standard location.
We can of course patch the install step downstream, but in my opinion it would be best just to fix it here 👍🏻
Hi @christian-heusel
Just for my education… if I look at the FHS custom packages should go to /opt.
Why are you not asking having Hyperion to be installed there?
@Lord-Grey usually only really big bundled packages (i.e. Android Studio, Zoom), which also ship their own dependency in the bundle, go to /opt/ and package-manager installed things which also link against the dependencies in /usr/lib go into /usr/bin.
I also already tried to provide some reasoning in the initial issue 😊
Bug report
Hyperion installs executables to
/usr/share/hyperion/bin
and just symlinks them to/usr/bin
Steps to reproduce
Build the application like you normally would and like we do in the ArchLinux
PKGBUILD
:See that the binaries are installed to
/usr/share/hyperion/bin
and that/usr/bin/
just contains symlinks to the afforementioned location.What is expected?
The compiled binaries should be installed to
/usr/bin
instead of/usr/share/hyperion/bin
as per the Filesystem Hierarchy Standard and the Arch Packaging Guidelines:/usr/share
: Architecture-independent (shared) data./usr/bin
: Non-essential command binaries (not needed in single-user mode); for all users.This was noticed because we have tooling in archlinux that scans through the binaries and notifies us when there are rebuilds needed (i.e. in this case for a protobuf update) where hyperion was missed because it has its binaries in this non-standard location.
We can of course patch the install step downstream, but in my opinion it would be best just to fix it here 👍🏻
What is actually happening?
See above
System
The text was updated successfully, but these errors were encountered: