Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 1/2] python3-dtschema: add dependency on pylibfdt
Date: Sun, 12 Feb 2023 15:51:09 -0500	[thread overview]
Message-ID: <20230212205108.GA22684@localhost> (raw)
In-Reply-To: <CADkTA4NwY6tb6HhA6LGk5dGxarbQzyrRS=H=i8u9TY8gBbAMZg@mail.gmail.com>

Hi Bruce,

On Fri 2023-02-10 @ 12:44:12 PM, Bruce Ashfield wrote:
> On Fri, Feb 10, 2023 at 9:25 AM Trevor Woerner <twoerner@gmail.com> wrote:
> >
> > dt-schema has a dependency on pylibfdt.
> >
> 
> FWIW. I find that the pypi libfdt lags quite a bit, and isn't updated
> often (that being said, there aren't really updates in dtc either, so
> it probably isn't an issue).
> 
> When I've been building it for supporting my other projects, I've
> ended up using the main dtc git, and meson to do the build and
> install.

One source base builds both dtc and pylibfdt.
The latest release of dtc is 1.7.0.
The dtc recipe in oecore is 1.6.1
The pypi index has an entry for pylibfdt 1.6.1, for which I've added a recipe.

I've been kicking around a couple things and could use some input. On the one
hand I tweaked the dtc_1.6.1 recipe in oecore to update it to dtc_1.7.0. I
also added metadata to additionally generate pylibfdt_1.7.0 from within the
same dtc_1.7.0 recipe, controlled by a PACKAGECONFIG.

How would you prefer to go forward?
- (I assume you would be happy to take an update of dtc_1.6.1 to dtc_1.7.0)
- updating dtc to also generate a python3-pylibfdt package
  - should this be controlled by a PACKAGECONFIG? or be build unconditionally?
- creating a separate python3-pylibfdt_1.7.0 recipe that uses the same sources
  but only generates the python3-pylibfdt package

I can put together a v3 when I know which path you'd prefer.

Best regards,
	Trevor


      reply	other threads:[~2023-02-12 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 14:25 [PATCH v2 1/2] python3-dtschema: add dependency on pylibfdt Trevor Woerner
2023-02-10 14:25 ` [PATCH v2 2/2] linux-yocto.inc: add dt-schema to devshell Trevor Woerner
2023-02-10 17:44 ` [OE-core] [PATCH v2 1/2] python3-dtschema: add dependency on pylibfdt Bruce Ashfield
2023-02-12 20:51   ` Trevor Woerner [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=20230212205108.GA22684@localhost \
    --to=twoerner@gmail.com \
    --cc=bruce.ashfield@gmail.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