From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] smack: new package.
Date: Fri, 25 Apr 2014 09:16:34 +0200 [thread overview]
Message-ID: <20140425091634.44faa70d@skate> (raw)
In-Reply-To: <87ha5i1o45.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Thu, 24 Apr 2014 22:14:34 +0200, Peter Korsgaard wrote:
> >> While reviewing these packages, I was indeed thinking of writing a
> >> "package addition check list" for the manual. But I'm wondering if this
> >> wouldn't replicate quite a lot of informations already in the manual,
> >> though it's true the idea of testing with some specific toolchain
> >> configurations isn't written anywhere.
>
> > I certainly think a checklist would be a good addition to the
> > manual. The checklist would not contain details, but only references
> > to other parts of the manual.
>
> > Adding a list of toolchain configurations to test packages with is
> > also on my todo list but I haven't gotten around these improvements
> > yet...
>
> Perhaps we need something like checkpatch.pl to test a package with the
> various toolchain combinations?
That could work with the packages that don't have crazy dependencies.
But as soon as the package starts depending on OpenGL or things like
that, it would be more difficult I believe.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-25 7:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 18:54 [Buildroot] [PATCH 0/2] SMACK: mandatory access control Eric Le Bihan
2014-04-20 18:54 ` [Buildroot] [PATCH 1/2] smack: new package Eric Le Bihan
2014-04-21 10:19 ` Thomas Petazzoni
2014-04-21 11:56 ` Eric Le Bihan
2014-04-21 11:55 ` Thomas Petazzoni
2014-04-21 12:49 ` Thomas De Schampheleire
2014-04-24 20:14 ` Peter Korsgaard
2014-04-25 7:16 ` Thomas Petazzoni [this message]
2014-04-20 18:54 ` [Buildroot] [PATCH 2/2] systemd: add SMACK support option Eric Le Bihan
2014-06-08 14:33 ` Thomas Petazzoni
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=20140425091634.44faa70d@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