From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Support additional user-defined package metadata
Date: Mon, 28 May 2012 10:44:42 +0100 [thread overview]
Message-ID: <1338198283.1964.320.camel@phil-desktop> (raw)
In-Reply-To: <1336915722-8155-1-git-send-email-ive.found@gmail.com>
On Sun, 2012-05-13 at 16:28 +0300, Leonid Borisenko wrote:
> Custom metadata field with supported firmware version(s) could be
> included into package control file for preventing of installing packaged
> modifications onto unsupported firmware.
Why isn't RDEPENDS sufficient for this?
p.
next prev parent reply other threads:[~2012-05-28 9:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 13:28 [PATCH 0/3] Support additional user-defined package metadata Leonid Borisenko
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 ` Phil Blundell [this message]
2012-05-28 18:46 ` [PATCH 0/3] " 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=1338198283.1964.320.camel@phil-desktop \
--to=philb@gnu.org \
--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