$out/lib/libexec?

$out/lib/libexec?

[Hartmut Goebel]

Hi,

I just discovered that some packages store programs in $out/lib/libexec
instead of $out/libexec. In my store, only KDE packages are effected.

Is it worth investigating? Or shall we just leave as it i?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: $out/lib/libexec?

[ng0]

I would leave it as it is, some applications require this layout,
I can only speak for what I work on - as it behaves this way - gnunet,
which would require too much to adjust to some arbitrary layout choice.

Re: $out/lib/libexec?

[Ludovic Courtès]

Hi,

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> I just discovered that some packages store programs in $out/lib/libexec
> instead of $out/libexec. In my store, only KDE packages are effected.
>
> Is it worth investigating? Or shall we just leave as it i?

IMO it would be nicer to have them install things to $out/libexec.

Ludo’.

Re: $out/lib/libexec?

[Hartmut Goebel]

Hi,

Am 26.11.19 um 11:32 schrieb Ludovic Courtès:
> IMO it would be nicer to have them install things to $out/libexec.
Given ng0's comment, I'll not put time into this for now.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: $out/lib/libexec?

[ng0]

To append some context to my comment, I've even tried to change
this in the build-system of gnunet, but after some discussion
it turned out to be a non-trivial task for design choices which
I amounts to bikeshed in the end. I wanted this change.

Searching for it in PLIST files, it's more common than one assumes,
but not common enough to work on a general solution (but I could be
wrong, and I did not mean to discourage you from work, just to show
one possible implication which isn't so obvious).