[Rpm-maint] [PATCH 04/12] Add new %policy section to the spec file format

[Bill Nottingham]

Steve Lawrence (slawrence at tresys.com) said: 
> > > Base:      Whether or not the module is a base module. Values can be
> > >            yes/1 or no/0. Defaults to no/0 if not given.
> > > 
> > > Name:      The name of the module. If not given, we assume the name is
> > >            the basename of the module file with file extensions removed
> > > 
> > > Obsoletes: One or more space-separated strings specifying which modules
> > >            are obsoleted by a module. Obsoleted modules are removed and
> > >            the new modules are installed. An example of when this might
> > >            be used is in policy renames. For example, if we renamed
> > > 		   foo.pp to bar.pp, we would specify that bar obsoletes foo. If
> > > 		   not specified, it is assumed the module obsoletes nothing.
> > > 
> > > Types:     One or more space-separated strings specifying which policy
> > >            types the module can work with. To explicitly state that a module
> > > 		   can work with any policy type, "default" can be specified as
> > > 		   the value. If not specified, we assume the module can work with
> > > 		   any policy type, and assign the types as "default".
> > 
> > How do you properly handle conflicts or requirements with various versions
> > of the base policy package?
> 
> We've realized this is a complicated topic we have not given enough
> attention and need to give this a bit more thought. We are open to any
> suggestions.

It almost sounds like it would be better to create actual packages
(like debuginfo) and synthesize the requires/provides/obsoletes/conflicts
there.

Bill