All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/1] scripts: Add gen-package.py
Date: Sun, 6 Mar 2016 23:22:48 +0100	[thread overview]
Message-ID: <20160306232248.4d37bcd2@free-electrons.com> (raw)
In-Reply-To: <1443426394-13595-2-git-send-email-judge.packham@gmail.com>

Dear Chris Packham,

On Mon, 28 Sep 2015 20:46:34 +1300, Chris Packham wrote:
> gen-package.py can be used to generate the initial skeleton Config.in
> and <package>.mk for a package based on its download URL.
> 
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
>  support/scripts/gen-package.py | 266 +++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 266 insertions(+)
>  create mode 100755 support/scripts/gen-package.py

Sorry for the very very slow feedback. To be honest, my opinion on this
is that a script that just generates the skeleton of a package is not
very useful.

What I find useful however are scripts to generate working packages
like we already have for CPAN Perl modules (scancpan script), and like
we will probably have for Python (see
http://patchwork.ozlabs.org/patch/501204/).

Another thing that would be useful is a "checkpackage" script, that
runs a bunch of verifications on a package (proper indentation, license
information filled in, etc.). But it is not trivial to do if you want
to check useful things.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-03-06 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28  7:46 [Buildroot] [RFC PATCH 0/1] Generating package skeletons Chris Packham
2015-09-28  7:46 ` [Buildroot] [RFC PATCH 1/1] scripts: Add gen-package.py Chris Packham
2016-03-06 22:22   ` Thomas Petazzoni [this message]
2016-03-07  7:40     ` Chris Packham
2016-03-07 23:07       ` 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=20160306232248.4d37bcd2@free-electrons.com \
    --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 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.