From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Added local package support.
Date: Fri, 27 Jul 2012 10:53:50 +0200 [thread overview]
Message-ID: <20120727085350.GA8573@mail.sceen.net> (raw)
In-Reply-To: <20120727101253.15d1af71@skate>
On Fri, Jul 27, 2012 at 10:12:53AM +0200, Thomas Petazzoni wrote:
> Le Fri, 27 Jul 2012 10:08:13 +0200,
> Arnout Vandecappelle <arnout@mind.be> a ?crit :
> > What do the others think?
>
> I am also a bit skeptical, but it's not yet a final and definitive
> opinion. Custom packages is one thing, but one also very often need to
> put stuff in board/ to keep kernel config, patches and various other
> stuff, though it's true nothing prevent you to use $(TOPDIR)/../ to
> keep track of all those things.
I don't really see the point of the feature either. Keeping custom files
in board and local packages in package/<company>/ is very easy to do and
should suit most people fine. Local packages (those that use the local
method) have one purpose : ease software development through the
buildroot environment. I don't think people spend that much time on the
.mk or Config.in files when using local packages. They spend time on
the packaged software itself.
--
Richard Braun
next prev parent reply other threads:[~2012-07-27 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 14:57 [Buildroot] [PATCH] Added local package support Avishay Orpaz
2012-07-24 4:24 ` Baruch Siach
2012-07-25 20:17 ` Avishay Orpaz
2012-07-25 23:18 ` Arnout Vandecappelle
[not found] ` <CAMkyJgA3+icHUKQ6AS==QQG--RuuptTjgy3KSdJvcwiAPxF3Rg@mail.gmail.com>
2012-07-27 8:08 ` Arnout Vandecappelle
2012-07-27 8:12 ` Thomas Petazzoni
2012-07-27 8:48 ` Simon Dawson
2012-07-27 8:53 ` Richard Braun [this message]
2012-07-29 7:02 ` Avishay Orpaz
2012-07-29 15:56 ` Arnout Vandecappelle
2012-07-29 16:34 ` Tzu-Jung Lee
2012-07-29 20:09 ` Avishay Orpaz
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=20120727085350.GA8573@mail.sceen.net \
--to=rbraun@sceen.net \
--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.