From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/fltk
Date: Thu, 28 Aug 2008 00:23:39 -0700 (PDT) [thread overview]
Message-ID: <19195469.post@talk.nabble.com> (raw)
In-Reply-To: <87vdxlu3zi.fsf@macbook.be.48ers.dk>
I think that generally the package directory is over populated.
I would like to see a rule along the lines of:
SubMenu Entry = package/subdir
i.e
package/base (minimum packages for uclibc)
package/x11r7 (X11r7 drivers)
package/xapps (x applications (only x))
package/utils (linux utilities)
package/network (network utilities)
package/block (block drivers etc like MTD
package/audio (alsa etc)
package/java (Already there)
package/xmlutils (libxml2 etc)
package/games (games)
package/graphics (GTK/QT/DirectFB packages)
I think 300 ish packages in one directory is a bit too much.
Each of these subdirs pretty much maps to a current menu entry
package/Config.in would become smaller and simpler
What do people think?
Dan
--
View this message in context: http://www.nabble.com/svn-commit%3A-trunk-buildroot-package-fltk-tp19189068p19195469.html
Sent from the BuildRoot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-08-28 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:19 [Buildroot] svn commit: trunk/buildroot/package/fltk jacmet at uclibc.org
2008-08-28 0:26 ` Hamish Moffatt
2008-08-28 5:02 ` Peter Korsgaard
2008-08-28 7:23 ` Daniel Laird [this message]
2008-08-29 0:38 ` Hamish Moffatt
2008-09-04 2:09 ` Hamish Moffatt
-- strict thread matches above, loose matches on Subject: below --
2008-03-20 16:54 ninevoltz at uclibc.org
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=19195469.post@talk.nabble.com \
--to=daniel.j.laird@nxp.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 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.