Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/bzip2
Date: Fri, 07 Mar 2008 09:24:54 +0100	[thread overview]
Message-ID: <1204878294.9461.88.camel@localhost> (raw)
In-Reply-To: <20080307000104.GA28350@cloud.net.au>

On Fri, 2008-03-07 at 11:01 +1100, Hamish Moffatt wrote:
> On Fri, Mar 07, 2008 at 12:56:09AM +0100, Ulf Samuelsson wrote:
> > ----- Original Message ----- 
> > From: "Hamish Moffatt" <hamish@cloud.net.au>
> > To: <buildroot@uclibc.org>
> > Sent: Friday, March 07, 2008 12:47 AM
> > Subject: Re: [Buildroot] svn commit: trunk/buildroot/package/bzip2
> > 
> > > Why move libbz2 from /lib to /usr/lib?
> > 
> > 
> > I think that this has been the trend for the last year.
> > A lot of packages has had this change.
> 
> I think some sort of policy document would be useful here. If libbz2 is
> in /usr/lib, that means no binaries in /bin or /sbin should use it
> really.
> 

Agreed.

Applications in /bin and /sbin which are dynamic linked must find their
libraries in /lib.

> Is /usr really irrelevant on a buildroot-sized system anyway? Should we
> just put everything in /lib, /bin and /sbin and forget it? (Perhaps even
> bin and sbin should merge.)
> 

No, some embedded systems have multiple flash partitions, and might use
one for /usr stuff and another for / stuff.

And please do not merge /bin and /sbin;

1. you must change a whole lot of Makefiles (make install)
2. some systems actually have multiple users ;)

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

  reply	other threads:[~2008-03-07  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 17:56 [Buildroot] svn commit: trunk/buildroot/package/bzip2 ninevoltz at uclibc.org
2008-03-06 23:47 ` Hamish Moffatt
2008-03-06 23:56   ` Ulf Samuelsson
2008-03-07  0:01     ` Hamish Moffatt
2008-03-07  8:24       ` Hans-Christian Egtvedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-20 22:25 ulf at uclibc.org
2007-06-25 14:53 aldot 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=1204878294.9461.88.camel@localhost \
    --to=hcegtvedt@atmel.com \
    --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