From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] X11 component versions
Date: Mon, 4 Feb 2013 23:54:38 +0100 [thread overview]
Message-ID: <20130204235438.0e1626e1@skate> (raw)
In-Reply-To: <CAOT3miKU=Wg6rQeyb4r6Lj6Yv9yDaHxqWCAtQ4_0VKGEw558Ug@mail.gmail.com>
Dear Nicolas Dechesne,
On Mon, 4 Feb 2013 23:45:50 +0100, Nicolas Dechesne wrote:
> this seems a better option indeed. i will try to cook a patch for
> that. i assume something like packages/x11apps should be a good
> package name, or perhaps x11_xorg_apps to make the distinction between
> apps from x.org and any other app that would use X11..
I am not quite sure about this solution, because it means that all
packages that are not part of official X.org releases would have to be
moved away from the package/x11r7 directory. For example, the tslib
driver I pointed, but they are also other X.org drivers that could be
added in the future and that are not part of official X.org releases.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-04 22:54 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
2013-02-04 22:45 ` Nicolas Dechesne
2013-02-04 22:54 ` Thomas Petazzoni [this message]
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=20130204235438.0e1626e1@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