From: Joshua Brindle <jbrindle@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Caleb Case <ccase@tresys.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Re: libsemanage Next Generation in Fedora 14?
Date: Fri, 26 Mar 2010 15:59:07 -0400 [thread overview]
Message-ID: <4BAD120B.3070705@tresys.com> (raw)
In-Reply-To: <4BACFED2.70508@redhat.com>
Daniel J Walsh wrote:
> Caleb and Josh,
>
> What do you think of putting the new version of libsemanage into F14? Do
> you think it is ready?
>
I don't think it is advisable. The current patchset makes use of a 'new'
kind of policy that is really the 3 parts of a refpolicy module combined
into a single file. The end system then pulls out all the interface
files and uses the entire Refpolicy build infrastructure to build a policy.
While that has uses (changing interfaces changes callers of the
interface, for example) it also means every end system would have to
have m4, sed, awk, checkpolicy and all the magic unicorns that are part
of building refpolicy.
Once we have a minimal CIL (without the transformation language, for
example) and a proper Refpolicy compiler much of this will be hidden
away behind the library it will be much more suitable.
I believe waiting until F15 is definitely the best idea, we never really
intended for a wider audience to use the current way because it is
non-ideal and has a number of hacks to make it work. It is mainly
available for people who want to work on it, see what it going to be
coming up or otherwise curious.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next parent reply other threads:[~2010-03-26 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BACFED2.70508@redhat.com>
2010-03-26 19:59 ` Joshua Brindle [this message]
2010-03-29 12:25 ` libsemanage Next Generation in Fedora 14? Daniel J Walsh
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=4BAD120B.3070705@tresys.com \
--to=jbrindle@tresys.com \
--cc=ccase@tresys.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.