Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package_rpm: Add %manifest support for spec generation.
Date: Fri, 29 Aug 2014 13:38:20 -0500	[thread overview]
Message-ID: <5400C89C.6070901@windriver.com> (raw)
In-Reply-To: <1409333994.29296.196.camel@ted>

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.

--Mark

> Signed-off-by: Ronan Le Martret <ronan@fridu.net>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/meta/classes/package_rpm.bbclass b/meta/classes/package_rpm.bbclass
> index eecfcb2..0f565ac 100644
> --- a/meta/classes/package_rpm.bbclass
> +++ b/meta/classes/package_rpm.bbclass
> @@ -389,6 +389,8 @@ python write_specfile () {
>               else:
>                   bb.note("Creating RPM package for %s" % splitname)
>                   spec_files_top.append('%files')
> +                if localdata.getVar('MANIFESTFILES', True):
> +                    spec_files_top.append('%%manifest %s' %  localdata.getVar('MANIFESTFILES', True))
>                   spec_files_top.append('%defattr(-,-,-,-)')
>                   if file_list:
>                       bb.note("Creating RPM package for %s" % splitname)
> @@ -495,6 +497,8 @@ python write_specfile () {
>               bb.note("Not creating empty RPM package for %s" % splitname)
>           else:
>               spec_files_bottom.append('%%files -n %s' % splitname)
> +            if localdata.getVar('MANIFESTFILES', True):
> +                spec_files_bottom.append('%%manifest %s' %  localdata.getVar('MANIFESTFILES', True))
>               spec_files_bottom.append('%defattr(-,-,-,-)')
>               if file_list:
>                   bb.note("Creating RPM package for %s" % splitname)
>
>



  reply	other threads:[~2014-08-29 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 17:39 [PATCH] package_rpm: Add %manifest support for spec generation Richard Purdie
2014-08-29 18:38 ` Mark Hatle [this message]
2014-08-29 21:51   ` Richard Purdie
2014-08-29 22:07     ` Mark Hatle

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=5400C89C.6070901@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox