[opensuse-packaging] Migration to /usr/libexec: openldap2
openldap2 was one of the affected packages in Factory:Staging:A. Is it acceptable to use %if to temporarily solve the problem of it currently being %{_libdir} but after %{_libexecdir}. And what about 32bit and 64bit in /usr/libexec afterwards? Questions from Michael Ströder (openldap2 packager) Callum Farmer {gmbr3} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 6/8/20 12:54 PM, Callum Farmer wrote:
openldap2 was one of the affected packages in Factory:Staging:A.
Is it acceptable to use %if to temporarily solve the problem of it currently being %{_libdir} but after %{_libexecdir}.
And what about 32bit and 64bit in /usr/libexec afterwards?
Questions from Michael Ströder (openldap2 packager)
Especially I wonder whether Andreas' statement is still true nowadays: https://lists.opensuse.org/opensuse-packaging/2014-12/msg00033.html Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, Jun 8, 2020 at 7:19 AM Michael Ströder <michael@stroeder.com> wrote:
On 6/8/20 12:54 PM, Callum Farmer wrote:
openldap2 was one of the affected packages in Factory:Staging:A.
Is it acceptable to use %if to temporarily solve the problem of it currently being %{_libdir} but after %{_libexecdir}.
And what about 32bit and 64bit in /usr/libexec afterwards?
Questions from Michael Ströder (openldap2 packager)
Especially I wonder whether Andreas' statement is still true nowadays:
https://lists.opensuse.org/opensuse-packaging/2014-12/msg00033.html
They are plugin libraries, so they should go into %_libdir/openldap. This is also consistent with how OpenLDAP is packaged in other Linux distributions. -- 真実はいつも一つ！/ 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
Fedora packages it as /usr/libexec with libs under /usr/lib or /usr/lib64 http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc32.aarc... which is the current plan. Is this allowed? On 08/06/2020, Neal Gompa <ngompa13@gmail.com> wrote:
On Mon, Jun 8, 2020 at 7:19 AM Michael Ströder <michael@stroeder.com> wrote:
On 6/8/20 12:54 PM, Callum Farmer wrote:
openldap2 was one of the affected packages in Factory:Staging:A.
Is it acceptable to use %if to temporarily solve the problem of it currently being %{_libdir} but after %{_libexecdir}.
And what about 32bit and 64bit in /usr/libexec afterwards?
Questions from Michael Ströder (openldap2 packager)
Especially I wonder whether Andreas' statement is still true nowadays:
https://lists.opensuse.org/opensuse-packaging/2014-12/msg00033.html
They are plugin libraries, so they should go into %_libdir/openldap. This is also consistent with how OpenLDAP is packaged in other Linux distributions.
-- 真実はいつも一つ！/ 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
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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/lib64
http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc32.aarc...
which is the current plan. Is this allowed?
It'd be more accurate to look at the spec file: * Fedora: https://src.fedoraproject.org/rpms/openldap/blob/master/f/openldap.spec * Mageia: http://svnweb.mageia.org/packages/cauldron/openldap/current/SPECS/openldap.s... It seems that the OpenLDAP autotools scripts misuse $libexecdir for library loadable plugin modules, when they should be in $libdir. -- 真実はいつも一つ！/ 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
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/lib64
http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc32.aarc...
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. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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/lib64
http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc32.aarc...
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 them "sharable", albeit indirectly. -- 真実はいつも一つ！/ 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
On 6/8/20 1:36 PM, Callum Farmer wrote:
Fedora packages it as /usr/libexec with libs under /usr/lib or /usr/lib64
http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc32.aarc...
This is the package for the client libs. There's a separate package containing slapd executable and the loadable backend and overlay modules: http://rpmfind.net/linux/RPM/fedora/32/x86_64/o/openldap-servers-2.4.47-4.fc... It seems those modules are installed in /usr/lib64/openldap. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Yep should all be kept in %{_libdir}. I'll set it to move back. On 08/06/2020, Michael Ströder <michael@stroeder.com> wrote:
On 6/8/20 1:36 PM, Callum Farmer wrote:
Fedora packages it as /usr/libexec with libs under /usr/lib or /usr/lib64
http://rpmfind.net/linux/RPM/fedora/32/aarch64/o/openldap-2.4.47-4.fc32.aarc...
This is the package for the client libs.
There's a separate package containing slapd executable and the loadable backend and overlay modules:
http://rpmfind.net/linux/RPM/fedora/32/x86_64/o/openldap-servers-2.4.47-4.fc...
It seems those modules are installed in /usr/lib64/openldap.
Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (4)
-
Callum Farmer -
Jan Engelhardt -
Michael Ströder -
Neal Gompa