RE: [PATCH 12/33] libsemanage: basic serialization

[Karl MacMillan <kmacmillan@mentalrootkit.com>]

On Tue, 2007-04-24 at 18:31 -0400, Joshua Brindle wrote:
> > From: Karl MacMillan [mailto:kmacmillan@mentalrootkit.com] 
> > 
> > On Mon, 2007-04-23 at 17:35 -0400, jbrindle@tresys.com wrote:
> > > plain text document attachment (semanage.serialize.diff) 
> > This is the 
> > > serialization infrastructure for libsemanage.
> > > 
> > 
> > We have talked about this in the past, but I think the 
> > duplication between libsemanage and libsepol should be 
> > removed. This is just ridiculous.
> > 
> 
> We haven't figured out how to remove it. There are lots of objects that
> are only in semanage (fcontext, seuser, etc) and many that are in sepol
> (user, boolean, etc).

We should move this into libsepol. I actually think that would make the
library split clearer.

>  We could do serialization of all sepol types (we
> are going to do that anyway for the new policy rep) and remove that
> stuff from libsemanage (I thought that was the plan anyway), for now
> this is how we did it. Hopefully that'll change. Both libraries are
> going to have to have serialization/unserialization infrastructure in
> any case.

Why? Just have a generic way to serialize lists (and perhaps name /
value pairs) in libsepol and all of the code falls out of libsemanage.

Karl


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