From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] recipes-app: rename example app and lib recipe to contain PV
Date: Tue, 2 Oct 2018 22:35:59 +0200 [thread overview]
Message-ID: <4bc18ffc-bd6b-4568-0a89-32c1fd8e9cd5@siemens.com> (raw)
In-Reply-To: <20181002181710.28456-1-henning.schild@siemens.com>
On 02.10.18 20:17, [ext] Henning Schild wrote:
> The PV of a package is best contained in its filename, that way a
> version bump would be chaning the file name. Also switch to using the
> git tag as SRCREV, now we can really just rename that file to update.
>
> Following that pattern we could also have multiple versions of the
> recipe in one tree.
>
> While we do not need all of this for Isar or for this simple example, be
> a good example for people reading those recipes.
NACK for the SRCREV changes.
That's an OE anti-pattern, (almost) like specifying a branch and ${AUTOREV}. You
need some sort of checksum (md5, sha256 for files, SHA1 for git commits) to
validate no one moved the upstream tag around.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-10-02 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 18:17 Henning Schild
2018-10-02 20:35 ` Jan Kiszka [this message]
2018-10-04 8:07 ` Henning Schild
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=4bc18ffc-bd6b-4568-0a89-32c1fd8e9cd5@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox