From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/ncurses
Date: Thu, 10 Apr 2008 09:06:29 +0200 [thread overview]
Message-ID: <871w5echoq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1207804466.6817.395.camel@nigel-x60> (Nigel Kukard's message of "Thu\, 10 Apr 2008 05\:14\:26 +0000")
>>>>> "Nigel" == Nigel Kukard <nkukard@lbsd.net> writes:
Hi,
>> Should be /usr/lib rather than /lib?
Nigel> The rest of the libs are being installed to /lib ... I don't like
Nigel> changing install paths, but I agree with you it should be /usr/lib ...
Nigel> anyone got any very good reason why ncurses should be installed in /lib?
The basic libncurses.co* is normally installed in /lib, but the extra
libs are in /usr/lib, E.G. on my Debian machine:
% dpkg -L libncurses5|grep .so|sort
/lib/libncurses.so.5
/lib/libncurses.so.5.6
/lib/libtic.so.5
/lib/libtic.so.5.6
/usr/lib/libform.so.5
/usr/lib/libform.so.5.6
/usr/lib/libmenu.so.5
/usr/lib/libmenu.so.5.6
/usr/lib/libpanel.so.5
/usr/lib/libpanel.so.5.6
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-10 7:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 11:38 [Buildroot] svn commit: trunk/buildroot/package/ncurses nkukard at uclibc.org
2008-04-09 22:35 ` Hamish Moffatt
2008-04-10 5:14 ` Nigel Kukard
2008-04-10 7:06 ` Peter Korsgaard [this message]
2008-04-10 9:10 ` Hamish Moffatt
-- strict thread matches above, loose matches on Subject: below --
2009-03-01 22:35 jacmet at uclibc.org
2009-01-23 23:02 ulf at uclibc.org
2009-01-24 6:33 ` Peter Korsgaard
2009-01-25 10:07 ` Thomas Lundquist
2009-01-25 20:56 ` Peter Korsgaard
2009-01-22 22:58 ulf at uclibc.org
2009-01-12 7:44 ulf at uclibc.org
2009-01-11 13:33 thomasez at uclibc.org
2008-07-01 19:24 jacmet at uclibc.org
2008-04-10 8:17 nkukard at uclibc.org
2008-04-10 5:14 nkukard at uclibc.org
2008-03-31 14:44 jacmet at uclibc.org
2008-03-07 13:57 ninevoltz at uclibc.org
2008-03-07 14:03 ` Peter Korsgaard
2008-03-06 18:19 ninevoltz at uclibc.org
2008-03-07 13:30 ` Peter Korsgaard
2007-07-23 8:33 ulf at uclibc.org
2007-06-25 16:56 aldot at uclibc.org
2007-06-25 16:35 aldot at uclibc.org
2007-06-25 15:38 aldot at uclibc.org
2007-06-23 13:56 aldot at uclibc.org
2007-03-07 14:46 aldot at uclibc.org
2007-01-30 17:47 aldot at uclibc.org
2007-01-22 23:52 andersen at uclibc.org
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=871w5echoq.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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