* Vincent Untz (vuntz@opensuse.org) [20091204 16:16]:

Hrm, I'm talking about libexecdir vs libdir, not libdir vs datadir :-)

Me too :) But I guess I should have phrased it better. But I think I'd better study the FHS again before I say more because as far as I remember, it says nothing about libexecdir. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Fri, Dec 04, 2009 at 09:42:32PM +0100, Cristian Morales Vega wrote:

2009/12/4 Philipp Thomas :

...

* Vincent Untz (vuntz@opensuse.org) [20091204 16:16]:

...

Hrm, I'm talking about libexecdir vs libdir, not libdir vs datadir :-)

Me too :) But I guess I should have phrased it better. But I think I'd better study the FHS again before I say more because as far as I remember, it says nothing about libexecdir.

FHS says: "/usr/lib includes object files, libraries, and ***internal binaries that are not intended to be executed directly by users or shell scripts***." That is the definition of libexecdir ("The directory for installing executable programs to be run by other programs rather than by users") from http://www.gnu.org/prep/standards/html_node/Directory-Variables.html

GNU says libexecdir should normally be $(exec_prefix)/libexec, that enters in contradiction with FHS.

GNU and FHS is not entirely compatible, but Linux distributions generally tend to follow FHS, which has been AFAIK designed in the glorious past to align all modern UNIXes together in this regard. FHS has no libexec and *generally* uses /usr/lib for this purpose. I'd expect SUSE to follow FHS like other Linux distributions (Debian is especially strict about this, and libexec in particular which is a prominent point of content), but of course this is up to our core packagers to decide - one could also say that it's too a minor point to waste time on. I was not able to quickly google out exact technical reasons for not including libexec, but I found some political ones... http://lists.zerezo.com/debian-devel/msg144902.html -- Petr "Pasky" Baudis A lot of people have my books on their bookshelves. That's the problem, they need to read them. -- Don Knuth -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On 24/05/11 21:16, Kyrill Detinov wrote:

Wednesday 25 May 2011

On Fri, 4 Dec 2009 21:42:32 +0100 Cristian Morales Vega wrote:

...

And we have: $ rpm --eval=%_libexecdir /usr/lib I see in http://old-en.opensuse.org/Packaging/RPM_Macros: %{_libexecdir} = %{_libdir}

What is the truth?

Preferred libexecdir on SUSE is usually /usr/lib/%{name} note NOT lib64 even on x86_64 (ignore old wiki) but this has to be defined in each specfile http://en.opensuse.org/openSUSE:Specfile_guidelines#Libexecdir Tejas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Wednesday 25 May 2011 On Wed, 25 May 2011 09:07:43 +0200 Vincent Untz wrote:

...

...

I see in http://old-en.opensuse.org/Packaging/RPM_Macros: %{_libexecdir} = %{_libdir}

This was the case a while ago, but it got changed (in 11.2, I'd say) to be /usr/lib on all architectures.

OK. Fixed in Wiki. -- WBR Kyrill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org