From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Ross Burton <Ross.Burton@arm.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] more ptest pedantry: why conditionally include "run-ptest" in SRC_URI?
Date: Tue, 13 Feb 2024 06:35:02 -0500 (EST) [thread overview]
Message-ID: <6c701a47-f76-e3d0-3ea8-1b44ec7617c0@crashcourse.ca> (raw)
In-Reply-To: <8C7A9199-D49B-4190-9D96-F060CD858C71@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On Mon, 12 Feb 2024, Ross Burton wrote:
> On 12 Feb 2024, at 06:39, Robert P. J. Day via lists.openembedded.org <rpjday=crashcourse.ca@lists.openembedded.org> wrote:
> > more annoying nitpickery ... here:
> >
> > https://git.openembedded.org/openembedded-core/tree/meta/recipes-extended/xz/xz_5.4.5.bb#n28
> >
> > it's not clear why someone would go to the trouble of conditionally
> > including run-ptest in SRC_URI as i would have thought the only
> > benefit would be to avoid the triviality of copying run-ptest into
> > WORKDIR, but beyond that, i don't see what the point is, and that's
> > the only recipe i've run across that bothers to do that.
> >
> > is there something more subtle happening here?
>
> No good reason, and I’d approve a patch that removed the
> conditionals on the grounds of cleaning up the recipe and ensuring
> that there’s less conditional paths through the recipe.
additional note in that, if a recipe inherits ptext, then it's silly
to conditionally include "run-ptest" in SRC_URI. but it's trickier if
something else in SRC_URI is included conditionally:
https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/flex/flex_2.6.4.bb#n18
without knowing what that patch does, it seems like you kind of have
to leave it as conditional. maybe other examples are more obvious.
rday
next prev parent reply other threads:[~2024-02-13 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 6:39 more ptest pedantry: why conditionally include "run-ptest" in SRC_URI? Robert P. J. Day
2024-02-12 6:47 ` Robert P. J. Day
2024-02-12 10:04 ` [OE-core] " Alexander Kanavin
2024-02-12 11:48 ` Ross Burton
2024-02-12 12:17 ` Robert P. J. Day
2024-02-12 12:55 ` Alex Kiernan
2024-02-12 14:46 ` Robert P. J. Day
2024-02-12 15:00 ` Alex Kiernan
2024-02-12 16:11 ` Ross Burton
2024-02-13 11:21 ` Robert P. J. Day
2024-02-13 16:25 ` Alex Kiernan
2024-02-13 11:35 ` Robert P. J. Day [this message]
2024-02-13 15:23 ` Peter Kjellerstedt
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=6c701a47-f76-e3d0-3ea8-1b44ec7617c0@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=Ross.Burton@arm.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