[Buildroot] [RFC] Unification of package comments on wchar, largefile, c++ support, thread, ... support

Michael Rommel rommel at layer-7.net
Fri Sep 6 14:38:33 UTC 2013


Hi all,

On Sep 6, 2013, at 16:34 , Thomas De Schampheleire <patrickdepinguin at gmail.com> wrote:

>> We have the choice between:
>> 
>> (1) All lower-case
>> 
>> comment "directfb needs a toolchain w/ ipv6, rpc, thread, wchar"
>> 
>> (2) Lower-case, except when it doesn't make sense (acronyms)
>> 
>> comment "directfb needs a toolchain w/ IPv6, RPC, thread, wchar"
>> 
>> (3) All upper-case
>> 
>> comment "directfb needs a toolchain w/ IPv6, RPC, THREAD, WCHAR"
> 
> All options are fine for me. I think the most important thing is that
> the user can map the comment onto the necessary configuration options
> in the toolchain menu.
> The second one is most balanced, I'm slightly leaning towards that.


I would like to have guidance for long package names, too, because I ran into the limit
for python-pyzmq which alone takes up considerable space and I needed three comments
to accommodate all...

  Michael.

-- 
Michael Rommel, Erlangen, Germany

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130906/95e61ffa/attachment-0002.html>


More information about the buildroot mailing list