From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Bump gpsd from version 2.95 to version 3.7
Date: Sat, 21 Jul 2012 15:26:03 +0200 [thread overview]
Message-ID: <20120721152603.01df6a00@skate> (raw)
In-Reply-To: <CAHt8ZCN-KYmfjbp4R3zwhLnRKrPUnrS1TziaECh8zvcEWZYddg@mail.gmail.com>
Le Sat, 21 Jul 2012 10:07:38 +0100,
Simon Dawson <spdawson@gmail.com> a ?crit :
> > Is there a non-ugly variant of this in the works?
>
> Not at present, I'm afraid. What would you suggest? Obviously, I can
> kick off the process of trying to get a fix into gpsd upstream. That
> could be a slow process; so, in the meantime, is it acceptable to have
> this (ugly, but small) patch in Buildroot?
Yes, it is perfectly acceptable. It's just that we generally try to
start the process of getting problems fixed upstream at the same time,
so hopefully at some point in the future (which may be a distant
point), such patches can be removed.
> >> +GPSD_DEPENDENCIES = host-scons host-python
> >
> > Do we really need a host-python here?
>
> You're quite right: there is no need for the Python version to be the
> same on host and target. I'll remove this spurious dependency in the
> next iteration of the patch.
Excellent, thanks.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-21 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 10:11 [Buildroot] [PATCH] Bump gpsd from version 2.95 to version 3.7 spdawson at gmail.com
2012-07-20 18:16 ` Thomas Petazzoni
2012-07-21 9:07 ` Simon Dawson
2012-07-21 13:26 ` Thomas Petazzoni [this message]
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=20120721152603.01df6a00@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