All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	David Gibson
	<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Marc-André Lureau"
	<marcandre.lureau-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"Bruce Ashfield"
	<bruce.ashfield-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH 0/4] Improve pylibfdt python packaging
Date: Wed, 10 Nov 2021 19:11:31 -0600	[thread overview]
Message-ID: <20211111011135.2386773-1-robh@kernel.org> (raw)

I'm interested in getting pylibfdt into PyPI and ran into a few issues
with pylibfdt using the python packaging tools. Primarily, pip didn't
work nor did setup.py sdist and bdist_wheel subcommands. This series
fixes those issues.

I've left meson calling setup.py intact for now, but think it's the
wrong way around. In fact, there's actually some efforts to make meson
the backend for pip/setuptools. I made several attempts to completely
eliminate putting files in the source tree without success. Also, I
noticed a meson install builds pylibfdt twice (though make may too).

I don't think I broke anything. Tests and installs both work with make
and meson.

Rob


Rob Herring (4):
  pylibfdt: Use setuptools instead of distutils
  pylibfdt: Use setuptools_scm for the version
  pylibfdt: Split setup.py author name and email
  pylibfdt: Move setup.py to the top level

 .gitignore                    |  4 ++++
 MANIFEST.in                   |  9 +++++++++
 pylibfdt/Makefile.pylibfdt    |  5 ++---
 pylibfdt/meson.build          |  5 ++---
 pylibfdt/setup.py => setup.py | 34 +++++++++++++---------------------
 5 files changed, 30 insertions(+), 27 deletions(-)
 create mode 100644 MANIFEST.in
 rename pylibfdt/setup.py => setup.py (56%)

-- 
2.32.0


             reply	other threads:[~2021-11-11  1:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  1:11 Rob Herring [this message]
     [not found] ` <20211111011135.2386773-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-11-11  1:11   ` [PATCH 1/4] pylibfdt: Use setuptools instead of distutils Rob Herring
2021-11-11  1:11   ` [PATCH 2/4] pylibfdt: Use setuptools_scm for the version Rob Herring
2021-11-11  1:11   ` [PATCH 3/4] pylibfdt: Split setup.py author name and email Rob Herring
2021-11-11  1:11   ` [PATCH 4/4] pylibfdt: Move setup.py to the top level Rob Herring
2021-11-11  3:41   ` [PATCH 0/4] Improve pylibfdt python packaging David Gibson
2021-11-11 14:08     ` Rob Herring
     [not found]       ` <CAL_JsqJ1gSzVH1OYU6kPCYDfg32j8whCKaOmo2VU8hsUFsJZuQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-11-11 14:22         ` Bruce Ashfield
2021-11-12  2:43         ` David Gibson
2021-11-12  4:01           ` Rob Herring
     [not found]             ` <CAL_JsqLuUMH16mow8bmYiPB60Cbci1cN_RhV3npYSqQzPhp97A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-11-13  3:19               ` David Gibson

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=20211111011135.2386773-1-robh@kernel.org \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=bruce.ashfield-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marcandre.lureau-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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.