Am 04.07.2018 um 14:31 schrieb Simon McVittie:
> Control: retitle 859724 debhelper: please consider using /usr/libexec in new
> compat levels
>
> On Thu, 06 Apr 2017 at 13:50:57 +0100, Simon McVittie wrote:
>> Using a non-architecture-varying libexecdir makes [things] a lot simpler
> ...
>> In Red-Hat-style (lib64) multilib, libexec programs are installed in
>> /usr/libexec regardless of architecture. I suspect that this means few
>> packages actually rely on having a multiarch-varying libexecdir, because
>> if they did, their co-installability would already be broken on
>> Red-Hat-style systems.
>>
>> For the next compat level please consider defaulting to:
>>
>> --libexecdir=\${prefix}/lib
>> --libdir=\${prefix}/lib/$multiarch (same as now)
>>Just wondering: What would be the benefit of such a change? Atm, if I look through my process list, packages seems to pretty much consistently use /usr/lib/foo/bar or /lib/foo/bar Some even hard-code that to be like that, e.g. systemd has rootlibexecdir = join_paths(rootprefixdir, 'lib/systemd') The result will be, that we now have daemons being started from /usr/libexec/, /lib/foo/ or /usr/lib/foo/ So we will have less consistency then we have now. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
