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] X11R7.5 git branch
Date: Tue, 2 Mar 2010 09:43:55 +0100	[thread overview]
Message-ID: <20100302094355.58cb7de8@surf> (raw)
In-Reply-To: <4B8AB776.40204@gmail.com>

Hi Paulius,

On Sun, 28 Feb 2010 20:35:34 +0200
Paulius Zaleckas <paulius.zaleckas@gmail.com> wrote:

> As we have discussed earlier I have put all my X11R7.5 work in:
> 
> git://gitorious.org/takeme-buildroot/takeme-buildroot.git x11r75
> 
> Should I post patch series to the list?

For me, having your git tree was enough.

Generally, it looks very good and I think it can be merged as is. I
appreciate the removal of all obsolete packages.

I have a few questions though :

 *) On many packages, but not all, you added FOOBAR_LIBTOOL_PATCH=NO.
    What has driven your choice of applying or not applying the libtool
    patch ?

 *) I imagine that all the patches you are dropping for the different
    packages have been merged upstream and are no longer needed ?

 *) I think the xf86-video-wsfb could just be removed. But this can be
    done later, if you don't want to rebase all your patch set.

 *) Concerning the dependency of xcb-util on gperf on the host, we have
    to decide whether gperf is a mandatory tool for Buildroot (in which
    case it should be added to toolchain/dependencies/dependencies.sh)
    or if we should build it, in which case, we need to add a
    host-gperf dependency.

 *) The xfont_font-util package should be fixed, as we discussed
    recently on the list. This post-install.sh script assuming that
    some tools are installed on the host is ugly. We must determine
    whether xfont_font-util should be built for the host, for the
    target or for both. But this can be done after merging your patch
    set, of course.

Thanks a lot for all this work!

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:[~2010-03-02  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28 18:35 [Buildroot] X11R7.5 git branch Paulius Zaleckas
2010-03-01 15:04 ` William Wagner
2010-03-01 20:47   ` Paulius Zaleckas
2010-03-02  9:08     ` William Wagner
2010-03-02  9:15       ` Thomas Petazzoni
2010-03-02 12:33       ` Paulius Zaleckas
2010-03-02  8:43 ` Thomas Petazzoni [this message]
2010-03-02  9:02   ` William Wagner
2010-03-02 12:31   ` Paulius Zaleckas
2010-03-08 13:30 ` Peter Korsgaard

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=20100302094355.58cb7de8@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