considered a bug in createrepo?
>
> There are a lot of Python files in /usr/share, but createrepo was one
> that's the most obvious to me (simply shelling out to a file in
> /usr/share). Similarly, there are a lot of executable files: (find
> /usr/share/ -executable -type f) Are
On Wed, 22 Apr 2015, Miloslav Trmač wrote:
now I'm curious.
Does it make more sense for these sort of scripts to live in
/usr/libexec, or in /usr/share?
/usr/libexec. From (info standards):
`libexecdir'
The directory for installing executable programs to be run by other
programs ra
> On Wed, Apr 22, 2015 at 8:06 AM, Miloslav Trmač wrote:
> > Hello,
> >> I confess I've only seen /usr/libexec used for add-on utilities, but
> >> now I'm curious.
> >>
> >> Does it make more sense for these sort of scripts to live in
> >> /usr/libexec, or in /usr/share?
> >
> > /usr/libexec. Fro
On Wed, Apr 22, 2015 at 8:06 AM, Miloslav Trmač wrote:
> Hello,
>> I confess I've only seen /usr/libexec used for add-on utilities, but
>> now I'm curious.
>>
>> Does it make more sense for these sort of scripts to live in
>> /usr/libexec, or in /usr/share?
>
> /usr/libexec. From (info standards)
Hello,
> I confess I've only seen /usr/libexec used for add-on utilities, but
> now I'm curious.
>
> Does it make more sense for these sort of scripts to live in
> /usr/libexec, or in /usr/share?
/usr/libexec. From (info standards):
> `libexecdir'
> The directory for installing executable p
Hi folks,
The Ceph package ships some utilities that are not intended to be run by users.
1. There's one utility that prepares Ceph's object storage daemon and
that is at is in /usr/libexec/ceph/ceph-osd-prestart.sh . The systemd
unit file calls that with "ExecStartPre=".
2. There are some other