Skip to content

Support additional user-defined package metadata

Ive Found openembedded-core 5 versions – In review

Get series with b4
b4 am CABnTX73jsT2yd74jkBzob4S8U_LdP_ju4VuLK+UiE-yvEOrP4g@mail.gmail.com

Versions newest first · linked by author and title

  1. v2 posting 3/31 patch 0 repliesNew
  2. v2 posting 2/32 patches 0 repliesSuperseded
  3. v3 Latest0 of 2 patches 2 repliesIn review
Earlier versions · 2
VersionPostedPatchesRepliesStatus
v2 posting 1/32 patches0 repliesSuperseded
v10 of 3 patches3 repliesSuperseded

Patches in v3 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PING v3] [PATCH 0/2] Support additional user-defined package metadata

Please, apply patches. They are small, atomic, tested and doesn't ruin anything, just adding the feature.

It is essential feature for us, so we've put efforts into implementing it. We'd like to see it merged into upstream. We are small group of enthusiasts, it will be very hard for us to maintain fork of OE (it will be impossible in fact).

Quoted 46 lines · Leonid Borisenko

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