All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: Markus Volk <f_l_k@t-online.de>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-gnome][PATCH 1/2] geary: initial add recipe
Date: Tue, 25 Jan 2022 17:45:02 +0100	[thread overview]
Message-ID: <1e2357fc2900c4eaef91943265baa293e0bfe76c.camel@pengutronix.de> (raw)
In-Reply-To: <622bf2f8-fd27-63ed-da25-89c6536a4f25@t-online.de>

Hi Markus,

On Tue, 2022-01-25 at 14:28 +0100, Markus Volk wrote:
> Hi Jan,
> 
> it is also allowed to use tags here.
> 
> SRCREV= "gnome-40.0" fetches the same code as
> 
> SRCREV = "e561775c1580a9f60a726355b2b897bfc9cb3382"

That's only true as long as nobody modifies that tag in the upstream repository
and isn't cryptographically secure. As far as I can see, no existing recipe in
meta-oe or oe-core uses a tag as SRCREV.

Additionally, https://docs.yoctoproject.org/singleindex.html#term-SRCREV warns:
"Note that if you want to build a fixed revision and you want to avoid
performing a query on the remote repository every time BitBake parses your
recipe, you should specify a SRCREV that is a full revision identifier and not
just a tag."

Regards,
Jan


  reply	other threads:[~2022-01-25 16:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220120202643.3827177-1-f_l_k@t-online.de>
2022-01-22 21:14 ` [oe] [meta-gnome][PATCH 1/2] geary: initial add recipe Andreas Müller
     [not found] ` <16CCB430AE750F17.20408@lists.openembedded.org>
2022-01-22 21:19   ` Andreas Müller
2022-01-23 12:07     ` Markus Volk
2022-01-25 12:25 ` Jan Lübbe
2022-01-25 13:28   ` Markus Volk
2022-01-25 16:45     ` Jan Lübbe [this message]
2022-01-25 17:00       ` Markus Volk
     [not found]         ` <3d81b267-c9c9-234a-5d74-15cd5ff754f9@gmail.com>
2022-01-25 17:38           ` Markus Volk

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=1e2357fc2900c4eaef91943265baa293e0bfe76c.camel@pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=f_l_k@t-online.de \
    --cc=openembedded-devel@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.