[pkg-bacula-devel] Fixing lintian tag executable-in-usr-lib?
Marcin Haba
marcin.haba at bacula.pl
Mon May 11 18:02:51 BST 2020
Hello Carsten, Hello Sven,
Thank you for your positive opinion about changing the path to /usr/sbin.
I am sure, this change will help users to easier find the json tools.
Best regards,
Marcin Haba (gani)
On Mon, May 11, 2020 at 9:16 AM Sven Hartge <sven at svenhartge.de> wrote:
>
> On 11.05.20 09:07, Carsten Leonhardt wrote:
> > Hi Marcin,
> >
> >> These json tools do not seem to be internal because Bacula components
> >> don't use them. And they can be used by shell scripts and by
> >> administrator.
> >>
> >> I am wondering why not use /usr/sbin path to store them:
> >
> > I think I chose the /usr/lib location because btraceback was already
> > there. Upstream installs them in /usr/sbin by default, OpenBSD in
> > /usr/local/sbin.
> >
> > I don't see why we couldn't move them to /usr/sbin, especially if it
> > makes your life easier.
>
> I agree. I only moved them to /usr/libexec because they where in
> /usr/lib, without further questioning if they should be in /usr/lib in
> the first place.
>
> I will prepare the needed changes.
>
> Grüße,
> Sven.
>
> _______________________________________________
> pkg-bacula-devel mailing list
> pkg-bacula-devel at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-bacula-devel
More information about the pkg-bacula-devel
mailing list