Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Added local package support.
Date: Fri, 27 Jul 2012 10:12:53 +0200	[thread overview]
Message-ID: <20120727101253.15d1af71@skate> (raw)
In-Reply-To: <50124C6D.8050608@mind.be>

Le Fri, 27 Jul 2012 10:08:13 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :

> >       I'm going to give comments on this patch, even though I'm not
> > sure if I would want to have this feature in buildroot.
> >
> >
> > Why? I think it's very convinient to leave buildroot untouched (and
> > easy to upgrade) and put the system specific packages in a
> > different place.
> 
>   That is currently usually done by (manually) adding a
> packages/<company name>/ directory which contains all the local
> packages, with a manually created Config.in.  So what this patch adds
> is mainly to build Config.in automatically.
> 
> >Anyway, if you don't intend to include the patch please let me know
> >so I won't bother to
> > make corrections.
> 
>   That's why I said immediately that I'm not a big fan of this
> feature.
> 
>   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.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-07-27  8:12 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 [this message]
2012-07-27  8:48             ` Simon Dawson
2012-07-27  8:53             ` Richard Braun
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=20120727101253.15d1af71@skate \
    --to=thomas.petazzoni@free-electrons.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