Mailinglist Archive: opensuse-packaging (74 mails)

< Previous Next >
Re: [opensuse-packaging] Proposal: Update rpm configuration to fix issues and rationalize configuration
  • From: Neal Gompa <ngompa13@xxxxxxxxx>
  • Date: Wed, 24 May 2017 07:26:17 -0400
  • Message-id: <>
On Wed, May 24, 2017 at 3:35 AM, Dominique Leuenberger / DimStar
<dimstar@xxxxxxxxxxxx> wrote:
On Wed, 2017-04-26 at 17:57 +0200, Michael Matz wrote:
As I said, modules (i.e. DSOs that are used with dlopen, not loaded
by would be placed into (subdirs of) libexec (conceptually (to
they are more similar to helper executables than shared libraries;
just happen to be implemented via shared library mechanisms)

Let's take a very practical example, showing that this can't work:

e.g libproxy (the library) and any of it's modules e.g. libproxy-

The lib is obviously in /usr/lib64/
the config module to it (arch dependent, loaded dynamically) in

libproxy being used by quite some low-level things is also provided as
biarch, so we have libproxy1-32bit (/usr/lib/

the 23bit variant on a 64bit system obviously needs to find it's
modules in a path that are not equal to the 64bit variant.

Putting that stuff into libexec sounds totally weird and would just
require to split stuff up even weirder...

=> modules loaded by a lib belong in my opinion to %{_libdir}/%{name}

I don't disagree with that. If it's a dylib/so file, then it belongs
in the private directory under %_libdir, especially if it's being
loaded by a library. libexec is for helper programs only. That is,
programs that are executed by other programs but should never be run
by users.

真実はいつも一つ!/ Always, there's only one truth!
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >