Re: policy under version control

[Tom <tom@lemuria.org>]

On Mon, Dec 01, 2003 at 10:13:35AM -0500, Stephen Smalley wrote:
> There is already a sourceforge CVS tree, and patches can be posted to
> the selinux list.

The problem I see with read-only CVS and a post-to-mailinglist approach 
is that it's non-trivial to maintain various sets of the same policy.

It seems that in the long run we won't be able to do with a single
default policy. We'll need a couple, or a modular approach. Something
very much like Debian's tasksel or other tools for other distributions
where you have 5-10 fields you can check what your machine is going to
be, and the relevant policy is then assembled automatically.


One of the things that I heard arch can do very well is allow people to
make local branches of a repository while still linking to it so that
their local changes automatically stay in sync with the upstream
repository.

That's just one idea. The more I talk and work with SE, and I work
mostly from a user perspective in that I very rarely dabble in the SE
code itself, the more I belief that the policy is the major point
deciding over broad acceptance or not.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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.