From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/1] scripts: Add gen-package.py
Date: Tue, 8 Mar 2016 00:07:08 +0100 [thread overview]
Message-ID: <56DE099C.9090404@mind.be> (raw)
In-Reply-To: <CAFOYHZDX9Ap8XSPuqKg8k-9+KA5qKB+DmhRH1FstXxMfkBG_7g@mail.gmail.com>
On 03/07/16 08:40, Chris Packham wrote:
> On Mon, Mar 7, 2016 at 11:22 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
[snip]
>> 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.
>
> Such a script would have helped me with some of my submissions.
Actually I have a skeleton of such a script lying around. Unfortunately, it
never got into a state where it would actually check much, so I never submitted
it. So I pushed it to [1] in case anyone is interested.
Regards,
Arnout
[1]
git fetch https://github.com/arnout/buildroot.git checkpackage
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2016-03-07 23:07 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
2016-03-07 7:40 ` Chris Packham
2016-03-07 23:07 ` Arnout Vandecappelle [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=56DE099C.9090404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox