All of lore.kernel.org
 help / color / mirror / Atom feed
From: Perceval <perceval_arenou@trimble.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] extend python3 manifest to add a module
Date: Wed, 14 Feb 2024 15:26:45 +0100	[thread overview]
Message-ID: <L4OU8S.IKKLTX9ZETHK2@trimble.com> (raw)
In-Reply-To: <8B0A80A4-7D4E-4ADE-A645-0C7DBBBDE8E7@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Thank you very much,
yes indeed :)

Perceval

On mer., févr. 14 2024 at 14:15:46 +0000, Ross Burton 
<Ross.Burton@arm.com> wrote:
> On 14 Feb 2024, at 14:03, Perceval <perceval_arenou@trimble.com 
> <mailto:perceval_arenou@trimble.com>> wrote:
>> 
>>  It seems that the dataclasses is not packaged in a dedicated 
>> package on the dunfell branch according to sources here  
>> <https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/python/python3/python3-manifest.json?h=dunfell>
>>  So it ends up in python3-misc which have a lot of things:
>>  $ oe-pkgdata-util find-path /usr/lib/python3.8/dataclasses.py
>>  python3-misc: /usr/lib/python3.8/dataclasses.py
>> 
>>  Should we package it in a dedicated package or another one? What 
>> would you suggest?
> 
> For master I just sent a patch moving it into -core, because it’s a 
> fairly fundamental package.
> 
> For dunfell, moving it now is probably not a great idea, but at least 
> you know now what package to RDEPEND on to get the class.
> 
> (or, you can RDEPEND on python3-modules and you get the entire 
> standard library)
> 
> Ross


[-- Attachment #2: Type: text/html, Size: 1479 bytes --]

      reply	other threads:[~2024-02-14 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  9:54 extend python3 manifest to add a module Perceval
2024-02-14 11:24 ` [yocto] " Ross Burton
2024-02-14 14:03   ` Perceval
2024-02-14 14:15     ` Ross Burton
2024-02-14 14:26       ` Perceval [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=L4OU8S.IKKLTX9ZETHK2@trimble.com \
    --to=perceval_arenou@trimble.com \
    --cc=Ross.Burton@arm.com \
    --cc=yocto@lists.yoctoproject.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.