All of lore.kernel.org
 help / color / mirror / Atom feed
* bbappend SRC_URI restriction request
@ 2021-07-15 23:03 jared_terry
  2021-07-16  0:53 ` [bitbake-devel] " Khem Raj
  2021-07-16 10:06 ` Ross Burton
  0 siblings, 2 replies; 3+ messages in thread
From: jared_terry @ 2021-07-15 23:03 UTC (permalink / raw)
  To: bitbake-devel

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

I'm building in Yocto 3.1.3 with bitbake 1.46.0 and I had a co-worker do a bbappend with this in it

PV = "231"
SRC_URI = "https://github.com/systemd/systemd-bootchart/releases/download/v${PV}/${PN}-${PV}.tar.xz"

now the hard part is this is a append applying over the top of systemd-bootchart_233.bb and since the SRC_URI = is a complete wipe of the value in the bb file its basically doing a forced override.

is it possible to set it up so this throws a warning?  This is something I would think would be very bad in a bbappend file and basically bypasses the bitbake-layers show-overlayed I've been using to detect who has forced an override of whats in poky.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [bitbake-devel] bbappend SRC_URI restriction request
  2021-07-15 23:03 bbappend SRC_URI restriction request jared_terry
@ 2021-07-16  0:53 ` Khem Raj
  2021-07-16 10:06 ` Ross Burton
  1 sibling, 0 replies; 3+ messages in thread
From: Khem Raj @ 2021-07-16  0:53 UTC (permalink / raw)
  To: jared_terry; +Cc: bitbake-devel

On Thu, Jul 15, 2021 at 4:03 PM <jared_terry@dell.com> wrote:
>
> I'm building in Yocto 3.1.3 with bitbake 1.46.0 and I had a co-worker do a bbappend with this in it
>
> PV = "231"
> SRC_URI = "https://github.com/systemd/systemd-bootchart/releases/download/v${PV}/${PN}-${PV}.tar.xz"
>
> now the hard part is this is a append applying over the top of systemd-bootchart_233.bb and since the SRC_URI = is a complete wipe of the value in the bb file its basically doing a forced override.
>
> is it possible to set it up so this throws a warning?  This is something I would think would be very bad in a bbappend file and basically bypasses the bitbake-layers show-overlayed I've been using to detect who has forced an override of whats in poky.

Technically, bbappends are not limited in any way than the main recipe
and hence we don't have such tools, have we decided that SRC_URIs can
not be overridden but only appended to then such a check would make
sense globally, however
if it matters to you perhaps you can think of writing a QA check in
insane bbclass perhaps.

>
> 
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [bitbake-devel] bbappend SRC_URI restriction request
  2021-07-15 23:03 bbappend SRC_URI restriction request jared_terry
  2021-07-16  0:53 ` [bitbake-devel] " Khem Raj
@ 2021-07-16 10:06 ` Ross Burton
  1 sibling, 0 replies; 3+ messages in thread
From: Ross Burton @ 2021-07-16 10:06 UTC (permalink / raw)
  To: jared_terry; +Cc: bitbake-devel

On Fri, 16 Jul 2021 at 00:03, <jared_terry@dell.com> wrote:
> is it possible to set it up so this throws a warning?  This is something I would think would be very bad in a bbappend file

Apart from when it's exactly what you want to do, of course. I've
definitely written appends which replace a tarball+patches with a git
repository.

> and basically bypasses the bitbake-layers show-overlayed I've been using to detect who has forced an override of whats in poky.

How does that bypass show-overlayed?

Ross

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-07-16 10:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-15 23:03 bbappend SRC_URI restriction request jared_terry
2021-07-16  0:53 ` [bitbake-devel] " Khem Raj
2021-07-16 10:06 ` Ross Burton

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.