Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] allow to define additional packaging metadata
Date: Sat, 18 Jan 2014 15:01:42 +0100	[thread overview]
Message-ID: <cover.1390052658.git.Martin.Jansa@gmail.com> (raw)

There is older patchset from Leonid which didn't get any response
on list, but is useful and still working.

It's good for extra packaging metadata like flag that device should
be restarted after package upgrade and it's packagemanager job to respect
them or not.

The following changes since commit 8163854adf87ac42a8f08ee25685d0ce1efb4724:

  oe-selftest: separated the SStateBase and SStateTests in different modules (2014-01-16 12:18:44 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib jansa/package-additional
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/package-additional

Leonid Borisenko (2):
  package.bbclass: add getter of additional metadata
  package_{ipk, deb, rpm}.bbclass: support additional user-defined
    metadata

 meta/classes/package.bbclass     | 11 +++++++++++
 meta/classes/package_deb.bbclass |  5 +++++
 meta/classes/package_ipk.bbclass |  5 +++++
 meta/classes/package_rpm.bbclass |  7 +++++++
 4 files changed, 28 insertions(+)

-- 
1.8.5.2



             reply	other threads:[~2014-01-18 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18 14:01 Martin Jansa [this message]
2014-01-18 14:01 ` [PATCH 1/2] package.bbclass: add getter of additional metadata Martin Jansa
2014-01-18 14:01 ` [PATCH 2/2] package_{ipk, deb, rpm}.bbclass: support additional user-defined metadata Martin Jansa

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=cover.1390052658.git.Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.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