From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3 of 4] manual generation: check dependencies first
Date: Thu, 19 Sep 2013 21:29:57 +0200 [thread overview]
Message-ID: <523B50B5.2080903@mind.be> (raw)
In-Reply-To: <20130919205718.45d3c7cc@skate>
On 19/09/13 20:57, Thomas Petazzoni wrote:
> Dear Thomas De Schampheleire,
>
> On Thu, 19 Sep 2013 18:27:34 +0200, Thomas De Schampheleire wrote:
>
>> I was thinking it could become a separate build target. But at that
>> time I didn't fully realize (and didn't check) that these lists are
>> actually included in the manual. So, that question is void now.
>
> No problem :)
>
>> Remains: how should we check for python argparse? Module argparse is
>> included from python-2.7 and python-3.2 onwards. It seems that Ubuntu
>> has been providing python-argparse for older python versions as well,
>> but IMO it is not needed to check for this explicitly. If you ask me,
>> I would simply check for python 2.7+ and 3.2+, but I'm open for
>> discussion.
>
> if ! python -c "import argparse" >/dev/null 2>&1 ; then
> echo "No Python, or argparse not available"
> exit 1
> fi
>
> something like that, no? It would cover both cases were argparse is
> part of the default Python installation and the cases were argparse was
> installed separately.
You could also download https://argparse.googlecode.com/hg/argparse.py
if needed, or include it in buildroot and at the following to the python
script:
try:
import argparse
except:
import compat_argparse as argparse
Unfortunately that only works down to python 2.5 - argparse.py is not
compatible with 2.4 or earlier.
Or, you could convert the script to optparse :-)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-09-19 19:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 10:47 [Buildroot] [PATCH 0 of 4] manual generation: misc changes Thomas De Schampheleire
2013-09-19 10:47 ` [Buildroot] [PATCH 1 of 4] manual generation: change capitalization of messages Thomas De Schampheleire
2013-09-19 15:37 ` Thomas Petazzoni
2013-09-20 13:17 ` Peter Korsgaard
2013-09-19 10:47 ` [Buildroot] [PATCH 2 of 4] manual generation: update help Thomas De Schampheleire
2013-09-19 15:37 ` Thomas Petazzoni
2013-09-20 13:17 ` Peter Korsgaard
2013-09-19 10:47 ` [Buildroot] [PATCH 3 of 4] manual generation: check dependencies first Thomas De Schampheleire
2013-09-19 11:43 ` Samuel Martin
2013-09-19 13:30 ` Thomas De Schampheleire
2013-09-19 14:28 ` Ryan Barnett
2013-09-19 15:08 ` Thomas De Schampheleire
2013-09-19 15:20 ` Ryan Barnett
2013-09-19 15:39 ` Thomas Petazzoni
2013-09-19 16:27 ` Thomas De Schampheleire
2013-09-19 18:57 ` Thomas Petazzoni
2013-09-19 19:29 ` Arnout Vandecappelle [this message]
2013-09-19 19:30 ` Arnout Vandecappelle
2013-09-20 18:23 ` Thomas De Schampheleire
2013-09-19 10:47 ` [Buildroot] [PATCH 4 of 4] manual generation: rename manual-txt into manual-text Thomas De Schampheleire
2013-09-19 15:40 ` Thomas Petazzoni
2013-09-19 15:49 ` Thomas De Schampheleire
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=523B50B5.2080903@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.