All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Pascal Huerst <pascal.huerst@gmail.com>
Cc: Rich Persaud <persaur@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Looking for a way to build latest tagged releases in recipes
Date: Wed, 8 Jan 2020 20:05:10 -0800	[thread overview]
Message-ID: <CAMKF1soSLjcZBoF2sg9cnTUWS2p5k3cqhR2Zo472tMOOeDiB1w@mail.gmail.com> (raw)
In-Reply-To: <baf60d23-56e5-72a2-f7f7-adb10c29a5f9@gmail.com>

On Wed, Jan 8, 2020 at 4:10 AM Pascal Huerst <pascal.huerst@gmail.com> wrote:
>
> Hey everyone!
>
> I'm looking for a way in yocto to build tagged releases or actually to
> build the newest tagged release from repositories.
>
> There is a way to specify a branch or a tag in a recipe, but no way to
> always clone the newest tagged release, that I'm aware of. I submitted a
> patch to bitbake's mailing list with a proposal [1], that would use
> bitbake's `latest_versionstring()`, to always find, fetch and build the
> latest tagged release. Unfortunately there wasn't much of a reaction on
> that proposal, so I'm taking a step back, collecting ideas on how this
> could be achieved properly.
>
> Please share your ideas...
>

while I understand the usecase, it has a downside, where a build can fail due to
someone pushing a new tag. I think we allow AUTOREV on branches which
is helpful in development and
CI systems. but deducing newest tag is useful when making releases,
this also means that it will bump the rev
in recipe automatically and people might get enticed to use it in
release process.

For such usecases, Maybe you can use floating tags ( like
'latest-release' or 'last-good' ) and move them when needed and lock
the recipes to use them to achieve what you want.

since use of AUTOREV in public recipes is discouraged, this does not
affect public layers as much
but I do worry about alternate workflows.

> Thanks!
> Pascal
>
> [1]
> http://lists.openembedded.org/pipermail/bitbake-devel/2019-December/020618.html
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


  reply	other threads:[~2020-01-09  4:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 12:10 Looking for a way to build latest tagged releases in recipes Pascal Huerst
2020-01-09  4:05 ` Khem Raj [this message]
2020-01-09 13:22   ` Pascal Huerst
2020-01-09 10:51 ` Richard Purdie
2020-01-09 11:26   ` Alexander Kanavin
2020-01-09 11:59   ` Pascal Huerst
2020-01-09 12:08     ` Richard Purdie
2020-01-09 13:36       ` Pascal Huerst
2020-01-13 16:23       ` chris.laplante
2020-01-15 20:59         ` chris.laplante
     [not found]           ` <5635f310-c6a0-1f4a-9fb9-05ac4813fdc1@gmail.com>
2020-01-16 17:42             ` chris.laplante
2020-01-16 20:21               ` chris.laplante
2020-01-18  1:11                 ` chris.laplante
2020-01-20  9:17                   ` Pascal Huerst
2020-01-24 15:44                 ` chris.laplante

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=CAMKF1soSLjcZBoF2sg9cnTUWS2p5k3cqhR2Zo472tMOOeDiB1w@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pascal.huerst@gmail.com \
    --cc=persaur@gmail.com \
    /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.