public inbox for bitbake-devel@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <rob.woolley@windriver.com>, <bitbake-devel@lists.openembedded.org>
Cc: "Alexander Kanavin" <alex@linutronix.de>
Subject: Re: [bitbake-devel] [PATCH 4/5] Add Python packaging files
Date: Wed, 21 Jan 2026 11:01:48 +0100	[thread overview]
Message-ID: <DFU6IL0O110G.ITYY9X55VEPV@bootlin.com> (raw)
In-Reply-To: <20260121024723.2634264-5-rob.woolley@windriver.com>

Hi,

On Wed Jan 21, 2026 at 3:47 AM CET, Rob Woolley via lists.openembedded.org wrote:
> This enables creating a pip package for PyPI with:
>
>     python3 -m build
>
> Signed-off-by: Rob Woolley <rob.woolley@windriver.com>
> ---
>  pyproject.toml |  3 +++
>  setup.cfg      | 40 ++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 43 insertions(+)
>  create mode 100644 pyproject.toml
>  create mode 100644 setup.cfg
>
> diff --git a/pyproject.toml b/pyproject.toml
> new file mode 100644
> index 00000000..4aff98bb
> --- /dev/null
> +++ b/pyproject.toml
> @@ -0,0 +1,3 @@
> +[build-system]
> +requires = ["setuptools>=61.0.0", "wheel"]
> +build-backend = "setuptools.build_meta"
> diff --git a/setup.cfg b/setup.cfg
> new file mode 100644
> index 00000000..3eaa3c49
> --- /dev/null
> +++ b/setup.cfg
> @@ -0,0 +1,40 @@
> +[metadata]
> +name = bitbake-setup
> +version = 2.16.0a1
> +author = OpenEmbedded BitBake Developers
> +author_email = bitbake-devel@lists.openembedded.org
> +description = bitbake-setup
> +long_description = file: README.md

I don't think we have a README.md file? Perhaps
doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst would be a
better candidate here?

> +long_description_content_type = text/markdown

This would be text/x-rst then.

> +url = https://github.com/openembedded/bitbake.git

It should probably be https://git.openembedded.org/bitbake/? The github version
is supposed to be a mirror only I think.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-01-21 10:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21  2:47 [PATCH 0/5] Package bitbake-setup for PyPI Rob Woolley
2026-01-21  2:47 ` [PATCH 1/5] gitignore: ignore Python packaging files Rob Woolley
2026-01-21  2:47 ` [PATCH 2/5] bitbake-setup: Move into Python module Rob Woolley
2026-01-21  2:47 ` [PATCH 3/5] bitbake-setup: Add wrapper script for bitbake_setup module Rob Woolley
2026-01-21  9:29   ` [bitbake-devel] " Alexander Kanavin
2026-01-21  2:47 ` [PATCH 4/5] Add Python packaging files Rob Woolley
2026-01-21  9:41   ` [bitbake-devel] " Alexander Kanavin
2026-01-21 10:01     ` Quentin Schulz
2026-01-21 10:07       ` Alexander Kanavin
2026-02-11 14:40       ` Rob Woolley
2026-02-12 11:38         ` Alexander Kanavin
2026-02-12 12:50           ` Quentin Schulz
2026-01-21  9:47   ` Quentin Schulz
2026-01-21 10:01   ` Antonin Godard [this message]
2026-01-21  2:47 ` [PATCH 5/5] bitbake-setup: Add the conditional script stanza Rob Woolley
2026-01-21  9:34 ` [bitbake-devel] [PATCH 0/5] Package bitbake-setup for PyPI Alexander Kanavin

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=DFU6IL0O110G.ITYY9X55VEPV@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=alex@linutronix.de \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=rob.woolley@windriver.com \
    /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