All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Ripple" <john.ripple@keysight.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta][PATCH] go-vendor.bbclass: Unpack into BP for destsuffix
Date: Thu, 18 Jun 2026 14:56:42 -0700	[thread overview]
Message-ID: <211612.1781819802325628623@lists.openembedded.org> (raw)
In-Reply-To: <CADkTA4MYBKZuuJ5iNHvq+SErx=mB3fz1UZq3VC1rofMemoUivw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

> 
> I have no particular issues with the change, but the commit log doesn't
> tell us why this is needed. Was something breaking ? is there any risk
> to the assumptions that other classes/recipes/layers may have made
> about the location of the unpacked files ?
> 

The go-vendor class was unpacking dependencies to ${UNPACKDIR}/git
and then needed S = "${UNPACKDIR}/git" to find the dependencies.
Changing the S variable caused the do_qa_unpack() ( https://git.openembedded.org/openembedded-core/tree/meta/classes-global/insane.bbclass#n1450 ) from insane.bbclass
to throw an error.

There shouldn't be any other assumptions from other classes/recipes/layers
that have been broken. The recipes I tested this change against used sources
fetched using the go_src_uri() function, regular git fetching, and local files.
There weren't any issues with moving to the go dependencies to the new
location. As far as I know nothing in openembedded-core uses the go-vendor
class making it trickier to test against a known baseline.

John

[-- Attachment #2: Type: text/html, Size: 1665 bytes --]

  reply	other threads:[~2026-06-18 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 21:31 [meta][PATCH] go-vendor.bbclass: Unpack into BP for destsuffix John Ripple
2026-06-18 21:33 ` [OE-core] " Bruce Ashfield
2026-06-18 21:56   ` John Ripple [this message]
2026-06-18 22:06     ` Richard Purdie
2026-06-18 22:12       ` John Ripple

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=211612.1781819802325628623@lists.openembedded.org \
    --to=john.ripple@keysight.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 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.