Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/4] devtool: account for sources in UNPACKDIR
Date: Thu, 24 Apr 2025 14:50:24 +0100	[thread overview]
Message-ID: <655a8640b7d8f528851f187558d19f8285e111e8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8eA1vnm6hO-AAn=xNEyMxrBGf48GTtiQOzW7w3yCqHKA@mail.gmail.com>

On Thu, 2025-04-24 at 14:41 +0200, Alexander Kanavin wrote:
> On Thu, 24 Apr 2025 at 14:14, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > > In the two examples above, what is UNPACKDIR set to?
> > 
> > Sorry, let me be more specific. What are the actual values of S and
> > WORKDIR for the different cases?
> 
> Can we step back for a bit? The original error is that 'devtool
> upgrade' breaks cryptically on recipes that set:
> 
> S = "${UNPACKDIR}/git" (instead of the usual WORKDIR/git).
> 
> (everything else being the defaults from oe-core).
> 
> Devtool, in this case, calculates the 'top level source' to be the
> same as UNPACKDIR, and breakage follows.
> 
> An example of such recipe in core is
> meta/recipes-devtools/rpm-sequoia/rpm-sequoia_1.7.0.bb

Stepping back further, we had this mess in devtool in the first place
as it could never work out which files in WORKDIR were "sources" which
it needed to handle carefully.

We now define UNPACKDIR as the place we unpack files to. devtool in
theory can therefore just redefine UNPACKDIR and WORKDIR and things
should 'just work'. The relation of the subpaths between the two should
remain the same.

This should therefore make the code in devtool simpler, not more
complex.

Your patch isn't doing that and I'm wondering if there are code paths
in there which are no longer needed if we handle UNPACKDIR correctly/as
intended.

So in summary, something isn't adding up here to me but I'm not yet
sure quite what.

Cheers,

Richard



  reply	other threads:[~2025-04-24 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 11:10 [PATCH 1/4] devtool: account for sources in UNPACKDIR Alexander Kanavin
2025-04-24 11:10 ` [PATCH 2/4] tcf-agent: update SRC_URI to https://gitlab.eclipse.org Alexander Kanavin
2025-04-24 11:10 ` [PATCH 3/4] libarchive: correct upstream version check Alexander Kanavin
2025-04-24 11:10 ` [PATCH 4/4] libunwind: use github-releases class to determine latest versions Alexander Kanavin
2025-04-24 11:32 ` [OE-core] [PATCH 1/4] devtool: account for sources in UNPACKDIR Richard Purdie
2025-04-24 11:44   ` Alexander Kanavin
2025-04-24 12:13     ` Richard Purdie
     [not found]     ` <18394019E7982924.8448@lists.openembedded.org>
2025-04-24 12:14       ` Richard Purdie
2025-04-24 12:41         ` Alexander Kanavin
2025-04-24 13:50           ` Richard Purdie [this message]
2025-04-24 17:36             ` Adrian Freihofer
2025-04-24 19:49               ` Alexander Kanavin
2025-04-24 19:36             ` Alexander Kanavin
2025-04-24 20:34               ` Richard Purdie
2025-04-25  8:33                 ` Alexander Kanavin
2025-04-25  9:31                   ` Richard Purdie
2025-04-25 17:29                     ` Alexander Kanavin
2025-04-30 10:20                       ` Richard Purdie

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=655a8640b7d8f528851f187558d19f8285e111e8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --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