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 13:14:29 +0100	[thread overview]
Message-ID: <64802f57b85b524ef1bab88b07a116e5af228d5c.camel@linuxfoundation.org> (raw)
In-Reply-To: <18394019E7982924.8448@lists.openembedded.org>

On Thu, 2025-04-24 at 13:13 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Thu, 2025-04-24 at 13:44 +0200, Alexander Kanavin wrote:
> > On Thu, 24 Apr 2025 at 13:32, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > 
> > > UNPACKDIR was meant to help with this. If devtool is changing the
> > > location, can't it just change UNPACKDIR and leave everything else
> > > alone? S will still be under UNPACKDIR/git even after devtool moves
> > > it?
> > 
> > Some recipes use
> > S = /path/to/workdir/git/sub/path
> > and some use
> > S = /path/to/workdir/unpackdir/git/sub/path
> > 
> > It's that 'git' part in the middle that needs to be extracted from
> > the final value of S and appended to UNPACKDIR (or WORKDIR), and then
> > the resulting path is moved by devtool to a workspace with shutil. I
> > probably don't fully understand the suggestion?
> 
> 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?

Cheers,

Richard


  parent reply	other threads:[~2025-04-24 12:14 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 [this message]
2025-04-24 12:41         ` Alexander Kanavin
2025-04-24 13:50           ` Richard Purdie
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=64802f57b85b524ef1bab88b07a116e5af228d5c.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