From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/ncurses
Date: Sun, 25 Jan 2009 11:07:22 +0100 [thread overview]
Message-ID: <20090125100722.GA14740@zelow.no> (raw)
In-Reply-To: <87ocxxi57i.fsf@macbook.be.48ers.dk>
On Sat, Jan 24, 2009 at 07:33:05AM +0100, Peter Korsgaard wrote:
>
> That looks odd. Why not simply always install the development stuff to
> target, and simply rely on the BR2_HAVE_DEVFILES setting to clean it
> up if it isn't desired?
I have to admit I'm a bit sceptic to this. It presumes that the
install scripts behave and we're able to get rid of all overhead when
we want to.
Thomas.
next prev parent reply other threads:[~2009-01-25 10:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:02 [Buildroot] svn commit: trunk/buildroot/package/ncurses ulf at uclibc.org
2009-01-24 6:33 ` Peter Korsgaard
2009-01-25 10:07 ` Thomas Lundquist [this message]
2009-01-25 20:56 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-03-01 22:35 jacmet at uclibc.org
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-04-09 11:38 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
2008-04-10 9:10 ` Hamish Moffatt
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=20090125100722.GA14740@zelow.no \
--to=lists@zelow.no \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.