On Mon, Jun 09, 2025 at 04:44:21PM +0200, Jerome BENOIT wrote:
> 
> ==================8><--------------------------------------------------------------------------------
> The package ships an executable file in /usr/lib.
> 
> Please move the file to /usr/libexec.
> 
> With policy revision 4.1.5, Debian adopted the Filesystem Hierarchy 
> Specification (FHS) version 3.0.
> 
> The FHS 3.0 describes /usr/libexec. Please use that location for executables.
> 
> [...]
> -----------------------><8===========================================================================
> 
> So my understanding is that executables in 
> /usr/lib/<archtriplet>/<package>/bin
> might be moved to /usr/libexec/<archtriplet>/<package> .

No they should be moved to /usr/libexec/<package>.
Neither the FHS nor Debian policy define /usr/libexec/<triplet>.
When multiarch was designed, it was decided multiarch would only cover
/lib and not /bin.

The problem with your approach is that it leads to all binaries in /usr/bin/ to
be moved to /usr/libexec/<triplet>/<package> and a wrapper script added to
/usr/bin/.

> # apt-file  find /lib/x86_64-linux-gnu | grep '/bin/' | wc -l
> gives on Sid
> 2576

You are counting packages multiple time. Consider

% apt-file  find /lib/ | grep '/bin/' |cut -d: -f1|sort -u|wc -l
439
vs
% apt-file  find /lib/x86_64-linux-gnu | grep '/bin/' |cut -d: -f1|sort -u|wc -l
60

If we make changes to GAP, we need to be able to justify them. So we need a 
real usecase.

Cheers,
Bill.

Reply via email to