Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ovidiu-Adrian Vancea <ovidiu.vancea@ni.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/3] ipk/deb/rpm: add kernel version to its dependencies
Date: Thu, 09 Jun 2016 16:23:13 +0100	[thread overview]
Message-ID: <1465485793.13979.125.camel@linuxfoundation.org> (raw)
In-Reply-To: <1465483659.36541.24.camel@ni.com>

On Thu, 2016-06-09 at 17:47 +0300, Ovidiu-Adrian Vancea wrote:
> At do_package time I can't modify the variables RDEPENDS, RRECOMMENDS
> and RSUGGESTS as stated in the following email:
> http://lists.openembedded.org/pipermail/bitbake-devel/2013-April/0034
> 16
> .html

In general that email is correct, changes to the variables won't
propergate between tasks.

There is an exception in the do_package -> do_package_write_xxx
process. These use emit_pkgdata() to save the data and
read_subpackage_metadata() to read the data back in.

Not all variables are covered, but the ones you mention above are. As
long as you modify them somewhere during do_package such as adding a
function to PACKAGESPLITFUNCS, the changes will persist in the
packaging.

> I've tried the smallest changes to these 3 fields but without
> success,
> confirming what was said in the email.
> I do manage to get the auto pr data (Version=4.1+git168+a7e53ecc27-
> r0.73 - notice r0.73) that I need to version the dependencies.
> 
> At variable loading time I could globally change RDEPENDS,
> RRECOMMENDS
> and RSUGGESTS but I can't get the auto pr data. Since I have no auto
> pr
> data, I can go as far as getting Version=4.1+gitAUTOINC+a7e53ecc27-r0
> (notice r0, not r0.73) which is incomplete.
> 
> The only place I've actually managed to insert the data was at
> package
> creation time (ipk, deb, rpm), which I agree is ugly but I've not
> found
> another to get me where I need.

See above, I believe you can change these values and other recipes do
this as long as its somewhere within the do_package task.

Cheers,

Richard


      reply	other threads:[~2016-06-09 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 16:08 [PATCH v2 0/3] ipk/deb/rpm: add kernel version to its dependencies Ovidiu-Adrian Vancea
2016-06-08 16:08 ` [PATCH v2 1/3] package_ipk.bbclass: " Ovidiu-Adrian Vancea
2016-06-08 16:08 ` [PATCH v2 2/3] package_deb.bbclass: " Ovidiu-Adrian Vancea
2016-06-08 16:08 ` [PATCH v2 3/3] package_rpm.bbclass: " Ovidiu-Adrian Vancea
2016-06-08 16:59 ` [PATCH v2 0/3] ipk/deb/rpm: " Richard Purdie
2016-06-09 14:47   ` Ovidiu-Adrian Vancea
2016-06-09 15:23     ` Richard Purdie [this message]

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=1465485793.13979.125.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ovidiu.vancea@ni.com \
    /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