From: "Guðni Már Gilbert" <gudnimar@noxmedical.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python3-manifest: prune python3-core
Date: Sun, 05 May 2024 04:41:10 -0700 [thread overview]
Message-ID: <1416.1714909270765233010@lists.openembedded.org> (raw)
In-Reply-To: <2135.1714611001880482361@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Hi again Tim, update from me regarding the scripts. TLDR: The manifest is out of date, and the python scripts are working as they should.
----
I've convinced myself the python scripts used to generate the manifest *are correct*. However, for anyone reading this, I can confirm the manifest is out of date. It would be nice to run the script on the next Python upgrade since it will remove a lot of dead file entries.
I couldn't see where I went wrong in my statement in the previous email I sent. I suspect two things 1) I wasn't looking at the correct "new" json output from the task 2) part to blame is I didn't fully enable all PACKAGECONFIGS, but this seems to mainly affect the tkinter and turtle packages.
On the bright side of things I did learn a few things so this wasn't a total waste of time for me :) Just makes things even more fun.
Best regards,
Gudni
[-- Attachment #2: Type: text/html, Size: 942 bytes --]
next prev parent reply other threads:[~2024-05-05 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 21:27 [PATCH] python3-manifest: prune python3-core Guðni Már Gilbert
2024-05-01 23:27 ` [OE-core] " Tim Orling
2024-05-02 0:50 ` Guðni Már Gilbert
2024-05-05 11:41 ` Guðni Már Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 21:16 Guðni Már Gilbert
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=1416.1714909270765233010@lists.openembedded.org \
--to=gudnimar@noxmedical.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).