From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] package/games/Config.in usage
Date: Thu, 17 Jun 2010 22:51:13 +0200 [thread overview]
Message-ID: <87mxutbcxq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100617222716.468feb2e@surf> (Thomas Petazzoni's message of "Thu, 17 Jun 2010 22:27:16 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> Me too.
Thomas> Why not, but in that case, we need non ambiguous names. I'm
Thomas> referring to the recent introduction of several Lua packages:
Thomas> some of them have fairly common names:
Thomas> http://git.buildroot.net/buildroot/commit/?id=50d6f2dde4db8c9d042294a09d5e8e120aec9987
Thomas> Maybe they should be named "lua-XXX" instead ?
Yes, sorry I forgot to answer your mail on this. It is not only the
directory name, but also the BR2_PACKAGE_* symbol that need to be
specific enough.
Thomas> Another strategy would be to mimick in the directory layout the
Thomas> organization of options in the menuconfig.
I find it quite handy to do a quick cd package/<package> when I need to
fix something in a package, without having to start make menuconfig to
figure out in what sub directory it is - The current package/multimedia
stuff kind of bothers me.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-06-17 20:51 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
2010-06-17 20:51 ` Peter Korsgaard [this message]
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=87mxutbcxq.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.