From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] /usr/libexec vs /usr/lib(32|64)/misc
Date: Tue, 29 Nov 2005 15:23:54 +0100 [thread overview]
Message-ID: <200511291523.55253@enterprise.flameeyes.is-a-geek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Hi all,
little question (that could start up a flame): what's the official status
of /usr/libexec directory?
I was told on IRC time ago to prefer /usr/$(get_libdir)/misc to libexec
because that's already ABI-specified... but I'm not really sure.
/usr/libexec is already used by many upstream packages, starting from FreeBSD
itself, and while it's true that /usr/$(get_libdir)/misc is ABI safe, I don't
really like thinking of moving executables in a subdirectory of lib for ABI's
sake.. or we'll end up having /usr/$(get_libdir)/binaries instead
of /usr/bin ...
So, as the documentation about that seems not to be clear, what's its status?
--
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-11-29 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 14:23 Diego 'Flameeyes' Pettenò [this message]
2005-11-29 14:53 ` [gentoo-dev] /usr/libexec vs /usr/lib(32|64)/misc Mike Frysinger
2005-11-29 15:18 ` Olivier Crête
2005-11-29 15:27 ` Mike Frysinger
2005-11-29 15:41 ` Thomas de Grenier de Latour
2005-11-29 16:05 ` Mike Frysinger
2005-11-29 15:48 ` Olivier Crête
2005-11-29 16:07 ` Mike Frysinger
2005-11-29 17:38 ` Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511291523.55253@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox