All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Konrad Weihmann <kweihmann@outlook.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] native python recipes using setuptools
Date: Tue, 16 Feb 2021 11:38:45 +0000	[thread overview]
Message-ID: <77fb6e42e9f858710792627660b116bafb168b2c.camel@linuxfoundation.org> (raw)
In-Reply-To: <AM9PR09MB46427C15B7F9F7652EA41605A8879@AM9PR09MB4642.eurprd09.prod.outlook.com>

On Tue, 2021-02-16 at 10:59 +0100, Konrad Weihmann wrote:
> I'm a bit puzzled at the moment - after 
> fd6a007efa7cb45101a66f294af81d9d33bb3fab in meta-openembedded I faced a 
> lot of changes in the behavior of native-only recipes (@RP yes the ones 
> that don't use BBCLASSEXTEND :-))
> 
> after this change I had a couple of dependency loops like
> 
> python3-my-recipe-native > python3 > ... > python3-my-recipe-native
> 
> and I could track it down to distutils3-base.bbclass [1].
> There for all recipes no matter what the set (I guess BBCLASSEXTEND 
> magic will solves that in the end) "python3-native python3" is set in 
> DEPENDS.
> 
> My question is, is that intended behavior or would it make sense to be 
> more explicit here, like
> 
> DEPENDS += "python3-native"
> DEPENDS_class-target += "python3"
> 
> ?
> 
> Mainly this happens when a globally inherited class requests a native 
> python3 package via DEPENDS (a not too uncommon use case for me).
> 
> Thoughts?

Definitely a bug, I've sent a patch. The DEPENDS would be needed for
nativesdk too and since it doesn't appear to require python3-native in
the native case, I didn't change that.

Cheers,

Richard


      reply	other threads:[~2021-02-16 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  9:59 native python recipes using setuptools Konrad Weihmann
2021-02-16 11:38 ` 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=77fb6e42e9f858710792627660b116bafb168b2c.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kweihmann@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.