[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-packaging
Subject:    Re: [opensuse-packaging] Migration to /usr/libexec: openldap2
From:       Neal Gompa <ngompa13 () gmail ! com>
Date:       2020-06-08 12:17:41
Message-ID: CAEg-Je8eWV7nYMsvbrVAt+nQc6siYuj8fYS3cePD5D4kPuFCuQ () mail ! gmail ! com
[Download RAW message or body]

On Mon, Jun 8, 2020 at 8:16 AM Jan Engelhardt <jengelh@inai.de> wrote:
>
> On Monday 2020-06-08 13:41, Neal Gompa wrote:
>
> >On Mon, Jun 8, 2020 at 7:36 AM Callum Farmer <callumjfarmer13@gmail.com>=
 wrote:
> >>
> >> Fedora packages it as /usr/libexec with libs under /usr/lib or /usr/li=
b64
> >>
> >> http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc3=
2.aarch64.html
> >>
> >> which is the current plan. Is this allowed?
> >
> >It seems that the OpenLDAP autotools scripts misuse $libexecdir for
> >library loadable plugin modules, when they should be in $libdir.
>
> As everyone should know, libexecdir only allows for a single bitness,
> and that's a design decision, since execve() can be called for arbitrary
> programs.
>
> A reason why openldap (or any other package) would "abuse" libexecdir
> for plugins is that said plugins may only be usable with one specific
> program anyway (usually the one that's sitting right in /usr/libexec)
> and not meant to be shared, even though it's a "shared object" in ld.so
> terms.

While that's true, AFAIK the loadable modules can be used by anything that
links the main OpenLDAP server or client libraries, which in effect makes t=
hem
"sharable", albeit indirectly.



--
=E7=9C=9F=E5=AE=9F=E3=81=AF=E3=81=84=E3=81=A4=E3=82=82=E4=B8=80=E3=81=A4=EF=
=BC=81/ Always, there's only one truth!
-- 
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]