public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: inherit allarch and use RDEPENDS
Date: Tue, 23 Aug 2016 15:15:39 +0000	[thread overview]
Message-ID: <0bf5343047414781867c8fc56c68ccba@XBOX02.axis.com> (raw)

I just stumbled on the mail below and it raised some questions:

> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Martin Jansa
> Sent: den 22 augusti 2016 16:21
> To: openembedded-core@lists.openembedded.org; Joe Slater
> Cc: openembedded-commits@lists.openembedded.org
> Subject: Re: [OE-core] [oe-commits] [openembedded-core] 01/02: systemd-
> compat-units: pkg_postinst() does not work
> 
> On Thu, Aug 18, 2016 at 03:52:33PM +0000, git@git.openembedded.org
> wrote:
> > rpurdie pushed a commit to branch master in repository openembedded-core.

[cut]

> > -RDPEPENDS_${PN} = "systemd"
> > +RDEPENDS_${PN} = "systemd"
> 
> This is good typo fix, but also causes allarch systemd-compat-units to
> RDEPENDS on TUNE_PKGARCH systemd as reported in:
> http://lists.openembedded.org/pipermail/openembedded-core/2016-August/125483.html
> 
> So either please exclude it in layer.conf or drop this runtime
> dependency completely.
> 
> --
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

This is the first I heard about limits to recipes that inherit allarch 
and also use RDEPENDS. So after I read the above, I went and read the 
documentation for the allarch class, which unfortunately did not make 
my understanding much clearer.

Am I to understand that a recipe that inherits allarch cannot have 
runtime dependencies on packages that are built differently per 
architecture or MACHINE? If so, what can it have runtime dependencies 
on? Only other allarch recipes? What are the design limitations behind 
this and is there anything that could be done to change the situation?

As an example, say that I have a recipe that only installs a static 
script, so inheriting allarch is a natural thing to do. However, for 
this script to work it must call a binary built by another recipe so 
it of course RDEPENDS on that other package. Are you saying this is 
wrong? Because that sounds odd to me as it severely limits the 
usefulness of the allarch class.

Another example would be a recipe that installs a static Perl script. 
Can it not inherit allarch while also have a runtime dependency on perl?

If the above is true, why are there no QA tests or similar that catch 
these kind of problems?

//Peter



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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 15:15 Peter Kjellerstedt [this message]
2016-08-23 15:32 ` inherit allarch and use RDEPENDS Richard Purdie
2016-08-24  6:35   ` Mike Looijmans
2016-08-24  7:18     ` Richard Purdie
2016-08-24 11:28       ` Mike Looijmans

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=0bf5343047414781867c8fc56c68ccba@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=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