Re: [PATCH] package_rpm: Add %manifest support for spec generation.

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2014-08-29 at 13:38 -0500, Mark Hatle wrote:
> On 8/29/14, 12:39 PM, Richard Purdie wrote:
> > From: Ronan Le Martret <ronan@fridu.net>
> >
> > The manifest file allow custom smack security for a package.
> >      https://wiki.tizen.org/wiki/Security/Application_installation_and_Manifest
> 
> I'm concerned with this simply because we're adding a very specific (non-oe) 
> mechanism into the mix.
> 
> I'd prefer if there was simple a "perform this generic action, which can add to 
> the .spec file"
> 
> The during the packaging (before writing the .spec) we can call the action and 
> it can insert the %manifest if appropriate.
> 
> That can then be distribution defined and work with any arbitrary mechanisms.

The rough plan forming in my (and other people's) minds is that we need
a proper python "spec" construction class.

If we had such a thing, customisations like this would be much easier,
we could also likely more easily reconcile some of the archiver srpm
pieces too.

Right now we don't have that, there are people needing to fork the whole
of package_rpm to add the few tweaks I've posted. I'm therefore minded
to make things easier. If/as or more like when we implement the class,
this kind of issue should go away.

Cheers,

Richard