Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 05/13] midori: remove configuration comment on X.org dependency
Date: Mon, 20 Jul 2009 10:45:10 +0200	[thread overview]
Message-ID: <20090720104510.43facc42@surf> (raw)
In-Reply-To: <874otaj4dw.fsf@macbook.be.48ers.dk>

Le Sat, 18 Jul 2009 01:06:51 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

> I don't completely agree. For toolchain issues such as WCHAR I think
> the comments can be very helpful as it isn't obvious why a package
> isn't visible.

True, but they're also very unpretty in the package list.

> For package dependencies, 'select' should be used for library
> dependencies. For huge things like X, I think it's OK to not show any
> comments as the user most likely doesn't expect an X package to be
> available if they haven't enabled X.

Yes.

> Related to this, I think we should move the X applications into a
> seperate sub menu.

Agreed. I've just started proposing some cleanups. More will follow if
I find some time.

> The stuff that can work with either directfb or X is a bit more
> tricky.

Definitely.

>  Thomas> Let's get rid of them, and let the user figure out using the
>  Thomas> help of each package available in the configuration system.
> 
> How? The package won't be visible if it has unmet dependencies.

Well, someone is currently working on xconfig support for Buildroot
(the patches should be coming out if I find the time to review them).
And xconfig allows to see all options, including the ones that cannot
be selected at the moment. Maybe a similar thing could be added to the
menuconfig interface ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-07-20  8:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 16:03 [Buildroot] [pull request] Pull request for branch xorg Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 01/13] xorg: reorganize the selection of the X.org server type Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 02/13] xorg: reindent configuration option details Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 03/13] xorg: remove useless configuration comment Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 04/13] xorg: simplify dependencies on X.org Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 05/13] midori: remove configuration comment on X.org dependency Thomas Petazzoni
2009-07-17 23:06   ` Peter Korsgaard
2009-07-20  8:45     ` Thomas Petazzoni [this message]
2009-07-17 16:03 ` [Buildroot] [PATCH 06/13] dillo: " Thomas Petazzoni
2009-07-17 23:21   ` Peter Korsgaard
2009-07-17 16:03 ` [Buildroot] [PATCH 07/13] matchbox: fix dependencies Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 08/13] xorg server: beautify list of dependencies Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 09/13] xorg server: remove dependencies Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 10/13] xorg: remove reference to non-existing BR2_PACKAGE_XSERVER_none Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 11/13] xorg: use BR2_PACKAGE_XORG instead of BR2_PACKAGE_XSERVER_none Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 12/13] xorg: remove references to non-existing configuration options Thomas Petazzoni
2009-07-17 16:03 ` [Buildroot] [PATCH 13/13] xorg: remove the XSERVER variable Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2009-07-24 21:30 [Buildroot] [pull request] Pull request for branch xorg Thomas Petazzoni
2009-07-24 21:30 ` [Buildroot] [PATCH 05/13] midori: remove configuration comment on X.org dependency Thomas Petazzoni

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=20090720104510.43facc42@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