All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 05/11] support: add kconfiglib python module
Date: Tue, 26 Feb 2013 21:18:41 +0100	[thread overview]
Message-ID: <512D18A1.3060308@mind.be> (raw)
In-Reply-To: <bd31d6b5313a660aaa80d596fdd3396e6a57751f.1361827174.git.s.martin49@gmail.com>

On 25/02/13 22:31, Samuel Martin wrote:
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> ---
>   support/pym/kconfiglib.py | 3772 +++++++++++++++++++++++++++++++++++++++++++++
>   support/pym/readme        |   14 +
>   2 files changed, 3786 insertions(+)
>   create mode 100644 support/pym/kconfiglib.py
>   create mode 100644 support/pym/readme
>
> diff --git a/support/pym/kconfiglib.py b/support/pym/kconfiglib.py
> new file mode 100644

  If you would put it in the same location as the gen-manual-lists.py 
script, then you don't need to mess with PYTHONPATH (the module's 
directory is always in PYTHONPATH).

[snip]

> diff --git a/support/pym/readme b/support/pym/readme
> new file mode 100644

  Obviously, if it moves from pym to scripts, it should be called 
README.kconfiglib or something similar.

> index 0000000..f44609c
> --- /dev/null
> +++ b/support/pym/readme
> @@ -0,0 +1,14 @@
> +Readme
> +======
> +
> +Kconfiglib
> +----------
> +
> +This is a python module fetched from:
> +
> +https://github.com/ulfalizer/Kconfiglib
> +commit: 417d62d1bf5fbfc7271c9d9b8dc2661b6332e288
> +
> +This module is not released under any explicit license, but it is a fair
> +asumption kconfiglib is released under the same license as the linux kernel,
> +i.e. GPLv2.

  Unfortunately, that's not a fair assumption... Perhaps we should mail 
the guy to verify.

  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

  reply	other threads:[~2013-02-26 20:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 21:31 [Buildroot] [pull request v2] Pull request for branch for-master/doc Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 01/11] manual: fix cross-refs Samuel Martin
2013-02-28 21:38   ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 02/11] manual: minor fix in patch-policy.txt Samuel Martin
2013-02-26  8:29   ` Thomas Petazzoni
2013-02-26  9:44     ` Samuel Martin
2013-02-26 11:01       ` Thomas Petazzoni
2013-02-26 11:15         ` Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 03/11] manual: misc. post-{build, image} scripts fixes Samuel Martin
2013-02-26  8:30   ` Thomas Petazzoni
2013-02-28 21:39   ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 04/11] working-with: board support Samuel Martin
2013-02-26 17:45   ` Arnout Vandecappelle
2013-02-28 21:39   ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 05/11] support: add kconfiglib python module Samuel Martin
2013-02-26 20:18   ` Arnout Vandecappelle [this message]
2013-02-25 21:31 ` [Buildroot] [PATCH 06/11] support/scripts: add gen-manual-lists.py Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 07/11] manual: add a make target 'manual-update-lists' Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 08/11] manual: cleanup appendix.txt Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 09/11] Makefile: add to the release target a warning about the manual updates Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 10/11] manual: update generated lists Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 11/11] Manual: add empty line after header in .mk files Samuel Martin
2013-02-28 21:39   ` 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=512D18A1.3060308@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.