From: Philip Tricca <flihp@twobit.us>
To: joe@deserted.net
Cc: yocto@yoctoproject.org
Subject: Re: [meta-selinux][PATCH 0/5] Remove python dependency from refpol.
Date: Wed, 09 Oct 2013 08:29:25 -0400 [thread overview]
Message-ID: <52554C25.4070205@twobit.us> (raw)
In-Reply-To: <20131009122318.GB5541@deserted.net>
Morning Joe
On 10/09/2013 08:23 AM, Joe MacDonald wrote:
> [[meta-selinux][PATCH 0/5] Remove python dependency from refpol.]
> On 13.10.09 (Wed 03:02) flihp@longhaul.twobit.us wrote:
>
>> The reference policy package currently pulls in a lot of python
>> stuff that isn't strictly necessary to boot an SELinux system and
>> load a policy. This is caused by the mix of python and C
>> utilities in policycoreutils.
>>
>> This patch set breaks the policycoreutils recipe up into
>> multiple packages, one for each utility. In this way we can have
>> the refpol etc pull in only the utilities necessary for normal
>> operation. This happens to be only the utilities written in C and
>> thus we can remove python completely in a minimal image.
>>
>> I've attempted to localize these changes as much as possible so
>> changes in this patchset outside of the policycoreutils recipe
>> are few. An example image reicpe is added to demonstrate a
>> minimal image with only the utilities required to load a policy
>> and manipulate the policy store (add / remove policy modules) at
>> runtime.
>
> Hey Philip,
>
> The patches never arrived in my mailbox and I don't see them in
> patchworks. Can you re-send, please?
I don't think this message made it to the list. Must have made it to
you and Mark though. I've resent and will send patches momentarily.
Cheers,
- Philip
next prev parent reply other threads:[~2013-10-09 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 3:02 [meta-selinux][PATCH 0/5] Remove python dependency from refpol flihp
2013-10-09 12:23 ` Joe MacDonald
2013-10-09 12:29 ` Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-09 12:23 Philip Tricca
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=52554C25.4070205@twobit.us \
--to=flihp@twobit.us \
--cc=joe@deserted.net \
--cc=yocto@yoctoproject.org \
/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.