From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Review of FOSDEM 2014 meeting action points
Date: Wed, 8 Oct 2014 18:43:14 +0200 [thread overview]
Message-ID: <20141008184314.50830272@free-electrons.com> (raw)
In-Reply-To: <CANQCQpbFSvHF9Q+Yo59H5NMVR31-JdR69Aao64popVHCt3QsVQ@mail.gmail.com>
Dear Matthew Weber,
On Wed, 8 Oct 2014 11:40:37 -0500, Matthew Weber wrote:
> > - SELinux. Still not merged, but not really pushed actively
> > anymore.
>
> We are preparing an updated SELinux patch set and hope to have it
> submitted in the Nov-Dec time frame (finally got some funding to
> finish this work). For this time around, we've been doing some extra
> testing in hopes the merge doesn't break things to badly. There are a
> number of RFC items that we'll be posting in the weeks to come
> (covering documentation, defconfig examples, handing target skeleton
> changes, etc.)
Great. SELinux is definitely interesting, but it's also a big thing,
with lots of packages with scary build systems that do not handle
cross-compilation very well. So it'll take a bit of time to review and
get merged. But we'll work with you to get this done.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-08 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 8:48 [Buildroot] Review of FOSDEM 2014 meeting action points Thomas Petazzoni
2014-10-08 8:54 ` Samuel Martin
2014-10-08 11:01 ` Maxime Hadjinlian
2014-10-08 16:14 ` Thomas Petazzoni
2014-10-08 16:24 ` Gustavo Zacarias
2014-10-08 16:18 ` Thomas Petazzoni
2014-10-08 11:17 ` Jeremy Rosen
2014-10-08 16:14 ` Thomas Petazzoni
2014-10-08 11:43 ` Thomas De Schampheleire
2014-10-08 16:16 ` Thomas Petazzoni
2014-10-08 16:40 ` Matthew Weber
2014-10-08 16:43 ` Thomas Petazzoni [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=20141008184314.50830272@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox