From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] package/games/Config.in usage
Date: Thu, 17 Jun 2010 22:27:16 +0200 [thread overview]
Message-ID: <20100617222716.468feb2e@surf> (raw)
In-Reply-To: <87zkytbwgo.fsf@macbook.be.48ers.dk>
On Thu, 17 Jun 2010 15:49:27 +0200
Peter Korsgaard <jacmet@uclibc.org> wrote:
> Julien> Hello,
> Julien> it seems package/games/Config.in is not used. Indeed package/Config.in
> Julien> do not "source" it but copy its content (line 76).
>
> Julien> What is the actual philosophy in BR: regroup packages by "classes" (ex
> Julien> games, multimedia...) in package/ subdirs and then source these
> Julien> sub-Config.in in package/Config.in or put all packages in package/ and
> Julien> organize the stuff in package/Config.in ?
> Julien> (I prefer the second one)
>
> Me too.
Why not, but in that case, we need non ambiguous names. I'm referring
to the recent introduction of several Lua packages: some of them have
fairly common names:
http://git.buildroot.net/buildroot/commit/?id=50d6f2dde4db8c9d042294a09d5e8e120aec9987
Maybe they should be named "lua-XXX" instead ?
Another strategy would be to mimick in the directory layout the
organization of options in the menuconfig.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-06-17 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 13:12 [Buildroot] package/games/Config.in usage Julien Boibessot
2010-06-17 13:49 ` Peter Korsgaard
2010-06-17 20:27 ` Thomas Petazzoni [this message]
2010-06-17 20:51 ` Peter Korsgaard
2010-06-21 7:31 ` Julien Boibessot
2010-06-21 8:28 ` Peter Korsgaard
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=20100617222716.468feb2e@surf \
--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