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] X11 component versions
Date: Mon, 4 Feb 2013 23:24:35 +0100	[thread overview]
Message-ID: <20130204232435.69179214@skate> (raw)
In-Reply-To: <CAOT3miJUfF3Oc2XFXJRiLCtMxtsHSWZWWLGvGyc+zNkqHGgnEw@mail.gmail.com>

Dear Nicolas Dechesne,

On Mon, 4 Feb 2013 22:37:36 +0100, Nicolas Dechesne wrote:

> well, what i would say is:
>  - for apps included in X11 release, take them all
>  - for other apps, it's a 'distro' choice to include it... so I would
> keep the one we have already, here I assume there must be a reason why
> they are there in BR already... and we can add new ones as needed...

We have two choices:

 * Move those apps outside of package/x11r7, so that package/x11r7 only
   contains packages that are part of official X11R7 releases. But we
   already have things like the x86-input-tslib package that is in
   package/x11r7, but is in fact not a X.org project at all.

 * Add additional exceptions for those applications in the xorg-release
   script, just to make the output of this script more meaningful.

I also feel like we have a lot of those old xapp_<something> and that
not many of them are actually useful beyond a good old xeyes to test
that your X.org server runs and that the mouse is working, and possibly
a few tools like xapp_xev and stuff like that.

But really, who cares about xman, xmh, xbiff, xcalc and similar things?

Best regards,

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

  parent reply	other threads:[~2013-02-04 22:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  9:44 [Buildroot] X11 component versions Nicolas Dechesne
2013-02-04 10:45 ` Will Wagner
2013-02-04 10:56   ` Nicolas Dechesne
2013-02-04 11:11     ` Will Wagner
2013-02-04 20:40       ` Thomas Petazzoni
2013-02-04 20:49         ` Nicolas Dechesne
2013-02-04 21:30           ` Thomas Petazzoni
2013-02-04 21:37             ` Nicolas Dechesne
2013-02-04 22:06               ` Arnout Vandecappelle
2013-02-04 22:41                 ` Nicolas Dechesne
2013-02-04 22:24               ` Thomas Petazzoni [this message]
2013-02-04 22:45                 ` Nicolas Dechesne
2013-02-04 22:54                   ` Thomas Petazzoni
2013-02-04 20:42       ` Nicolas Dechesne
2013-02-04 22:46 ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2013-03-12  8:52 Jesper Birksø Bækdahl
2013-03-18  8:05 ` Arnout Vandecappelle

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=20130204232435.69179214@skate \
    --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