Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/fltk
Date: Thu, 4 Sep 2008 12:09:40 +1000	[thread overview]
Message-ID: <20080904020940.GA17987@cloud.net.au> (raw)
In-Reply-To: <87vdxlu3zi.fsf@macbook.be.48ers.dk>

On Thu, Aug 28, 2008 at 07:02:09AM +0200, Peter Korsgaard wrote:
>  Hamish> I think those comments are kind of helpful. Otherwise, if you know a
>  Hamish> package exists but can't find it in menuconfig, you need to open up
>  Hamish> Config.in to find the dependencies.
> 
> Sometimes they are, but having tons of those lines listed for all X
> programs when you haven't selected X is imho not.

That's fair.

> We should probably move X applications / libraries to it's own sub
> menu.

Good solution, then all the X applications could be disabled and
replaced with a single comment if X libraries are not enabled.

>  Hamish> Alternatively the package could use select instead of depends.
> 
> Yeah, but that wouldn't work here as there's multiple providers of X
> (and anyway, including a monster like X behind your back isn't really
> userfriendly either).

Very true!

thanks
Hamish

-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  parent reply	other threads:[~2008-09-04  2:09 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
2008-08-29  0:38     ` Hamish Moffatt
2008-09-04  2:09     ` Hamish Moffatt [this message]
  -- 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=20080904020940.GA17987@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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