All of lore.kernel.org
 help / color / mirror / Atom feed
From: "tomzy" <tomasz.zyjewski@3mdeb.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH 2/2] python3-uefi-firmware: add recipe for version 1.9
Date: Thu, 01 Dec 2022 00:37:40 -0800	[thread overview]
Message-ID: <13060.1669883860311865393@lists.openembedded.org> (raw)
In-Reply-To: <61866268-84e1-7ad5-5992-f78281e1bb3a@gmail.com>

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

On Wed, Nov 30, 2022 at 09:08 PM, Khem Raj wrote:

> 
> On 11/29/22 11:29 PM, tomzy wrote:
> 
>> On Fri, Nov 25, 2022 at 3:44 AM tomzy <tomasz.zyjewski@...
>> <mailto:tomasz.zyjewski@...>> wrote:
>> 
>> Install uefi-firmware-parser tool
>> 
>> Signed-off-by: Tomasz Żyjewski <tomasz.zyjewski@...
>> <mailto:tomasz.zyjewski@...>>
>> ---
>> .../python/python3-uefi-firmware_1.9.bb
>> < http://python3-uefi-firmware_1.9.bb >         | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>> create mode 100644
>> meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
>> < http://python3-uefi-firmware_1.9.bb >
>> 
>> diff --git
>> a/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
>> < http://python3-uefi-firmware_1.9.bb >
>> b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
>> < http://python3-uefi-firmware_1.9.bb >
>> new file mode 100644
>> index 000000000000..ba3124b36e60
>> --- /dev/null
>> +++
>> b/meta-python/recipes-devtools/python/python3-uefi-firmware_1.9.bb
>> < http://python3-uefi-firmware_1.9.bb >
>> @@ -0,0 +1,17 @@
>> +SUMMARY = "Various data structures and parsing tools for UEFI
>> firmware."
>> +DESCRIPTION = "This package contains Python UEFI firmware parser
>> tool. The \
>> +UEFI firmware parser is a simple module and set of scripts for
>> parsing, \
>> +extracting, and recreating UEFI firmware volumes. This includes
>> parsing \
>> +modules for BIOS, OptionROM, Intel ME and other formats too."
>> +HOMEPAGE = " https://github.com/theopolis/uefi-firmware-parser
>> < https://github.com/theopolis/uefi-firmware-parser>"
>> +AUTHOR = "Teddy Reed <teddy@... <mailto:teddy@...>>"
>> +LICENSE = "BSD-2-Clause & BSD-3-Clause"
>> +LIC_FILES_CHKSUM =
>> "file://setup.py;md5=90fa5bae1547550f1c1993f651eda955"
>> +
>> +SRC_URI =
>> " https://files.pythonhosted.org/packages/7e/b4/a4ec646d24a1aad709fdb83de6e5eddd6cb24faec02f3a94a3af3b0aba28/uefi_firmware-
>> ${PV}.tar.gz < https://files.pythonhosted.org/packages/7e/b4/a4ec646d24a1aad709fdb83de6e5eddd6cb24faec02f3a94a3af3b0aba28/uefi_firmware-
>> $%7BPV%7D.tar.gz>"
>> 
>> If you’re fetching from  pythonhosted, you could very likely
>> simplify the recipe by inheriting pypi bbclass
>> 
>> +SRC_URI[md5sum] = "ee5011b4d0bcb0eb7c06295e0107894f"
>> 
>> These days, we only really use the sha256sum
>> +SRC_URI[sha256sum] =
>> "234119dd92780c67cce3b664e86119c41d0b2af188d7f372b69789b32c5d5cd0" +
>> +S = "${WORKDIR}/uefi_firmware-${PV}" + +inherit setuptools3 -- 2.25.1
>> 
>> 
>> Used git fetcher here, I just send PATCH V2, not sure if it visible on
>> mailing list.
> 
> Its not. Where did you send it ?

I must had something wrong with my email settings. Now it is sent. Just pushed V3 because of typo in subject-prefix.

uefi-firmware: https://lists.openembedded.org/g/openembedded-devel/message/99883

binwalk: https://lists.openembedded.org/g/openembedded-devel/message/99882

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

  reply	other threads:[~2022-12-01  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 11:44 [meta-python][PATCH 1/2] python3-binwalk: add recipe for version 2.3.3 Tomasz Żyjewski
2022-11-25 11:44 ` [meta-python][PATCH 2/2] python3-uefi-firmware: add recipe for version 1.9 Tomasz Żyjewski
2022-11-26 23:17   ` [oe] " Tim Orling
2022-11-30  7:29     ` tomzy
2022-11-30 20:08       ` [oe] " Khem Raj
2022-12-01  8:37         ` tomzy [this message]
2022-11-26 23:18 ` [oe] [meta-python][PATCH 1/2] python3-binwalk: add recipe for version 2.3.3 Tim Orling
2022-11-30  7:28   ` tomzy

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=13060.1669883860311865393@lists.openembedded.org \
    --to=tomasz.zyjewski@3mdeb.com \
    --cc=openembedded-devel@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.