Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonid Borisenko <ive.found@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Support additional user-defined package metadata
Date: Sun, 13 May 2012 16:28:40 +0300	[thread overview]
Message-ID: <1336915722-8155-1-git-send-email-ive.found@gmail.com> (raw)

I'm an owner of Kindle Touch. It's basically a computer with ARM
Cortex-A8 based CPU and Linux. There is a [small] community of
enthuasists developing homebrew modifications for stock software. For
distributing of these modifications .ipk package format had been chosen
with OE as build infrastructure.

There are already several firmware versions for device and some more are
expected. Every firmware can introduce unpredictable changes, so
modifications for previous firmware versions could stop working.

Custom metadata field with supported firmware version(s) could be
included into package control file for preventing of installing packaged
modifications onto unsupported firmware.

But OE currently doesn't allow to define additional package metadata in
recipes. Patch fixes it.

There is already RPMSPEC_PREAMBLE variable used in package_rpm.bbclass.
I think, it is still useful for defining custom macros in header of spec
file (while additional user-defined metadata is placed somewhere between
common tags).

I didn't found any way to define newline character inside variable value
and it is needed to allow multiple [one-line] metadata fields/tags. So
I've used ability of OE to split list-typed variables (and re-joined
splitted value with real newline character).

The following changes since commit cab85fd0b481cdbf36477348de75352be3f38ca2:

  gdk-pixbuf: Drop unneeded RPROVIDES (2012-05-12 11:23:27 +0100)

up to 052d78ed7f986e76afb1ce6ef02e94ba1bbc9719:

  package_{ipk, deb, rpm}.bbclass: support additional user-defined metadata (2012-05-13 14:51:26 +0300)

----------------------------------------------------------------
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(+)




             reply	other threads:[~2012-05-13 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 13:28 Leonid Borisenko [this message]
2012-05-13 13:28 ` [PATCH 1/2] package.bbclass: add getter of additional metadata Leonid Borisenko
2012-05-13 13:28 ` [PATCH 2/2] package_{ipk, deb, rpm}.bbclass: support additional user-defined metadata Leonid Borisenko
2012-05-18 18:34 ` [PATCH 0/3] Support additional user-defined package metadata Ive Found
2012-05-28  6:40 ` [PING v2] [PATCH 0/2] " Ive Found
2012-05-28  9:44 ` [PATCH 0/3] " Phil Blundell
2012-05-28 18:46   ` Ive Found
2012-06-06  7:28 ` [PING v3] [PATCH 0/2] " Ive Found
2012-11-03 23:01   ` Sebastian Krzyszkowiak
2012-11-06 23:58     ` Otavio Salvador
2012-11-16 18:29       ` [PATCH v2 0/2] Support additional user-defined metadata Leonid Borisenko
2012-11-16 18:29         ` [PATCH v2 1/2] package.bbclass: add getter of additional metadata Leonid Borisenko
2012-11-16 18:29         ` [PATCH v2 2/2] package_{ipk, deb, rpm}.bbclass: support additional user-defined metadata Leonid Borisenko
2012-12-07 17:28         ` [PING] [PATCH v2] Support " Leonid Borisenko

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=1336915722-8155-1-git-send-email-ive.found@gmail.com \
    --to=ive.found@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