From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] package: remove 'v' prefix from github-fetched packages
Date: Thu, 20 Jun 2019 08:31:10 +0200 [thread overview]
Message-ID: <20190620083110.4986e5fa@windsurf> (raw)
In-Reply-To: <35a7118e-cdf1-b29e-bceb-6c02ecef187e@mind.be>
On Wed, 19 Jun 2019 22:50:01 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> Note: I double-checked: apparently, release-monitoring really *never* has a v
> in front of the version. There are a few other things though, e.g. DIRECTFB_
I'm not sure what you referring to regarding DIRECTFB_.
However, release-monitoring doesn't overall has something that enforces
keeping or not keeping a version prefix. It is the definition of each
package on release-monitoring that details how to extract the version,
typically stripping any prefix. Because this is the norm on
release-monitoring (stripping the prefix), any package definition that
does not comply with this should probably be fixed on
release-monitoring.
My point is that if there is a bogus package definition on
release-monitoring, we should not work it around in Buildroot, but fix
it on release-monitoring itself.
> It would also be nice if we had some formal way of checking that new packages
> do this correctly. Actually, it would be good if pkg-stats could generate a
> report in a human-readable format so it could be used as part of the review flow
> to check if the mapping with release-monitoring is OK (plus all the other things
> pkg-stats evaluates).
Hm, yes, could be an interesting idea. Just a new pkg-stats option ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-20 6:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 6:42 [Buildroot] [PATCH 0/4] Sanetize packages version Victor Huesca
2019-06-12 6:42 ` [Buildroot] [PATCH 1/4] package: remove 'v' prefix from github-fetched packages Victor Huesca
2019-06-19 20:50 ` Arnout Vandecappelle
2019-06-20 6:31 ` Thomas Petazzoni [this message]
2019-06-20 19:33 ` Arnout Vandecappelle
2019-06-20 19:46 ` Thomas Petazzoni
2019-06-20 21:07 ` Arnout Vandecappelle
2019-06-20 11:51 ` Victor Huesca
2019-06-20 19:31 ` Arnout Vandecappelle
2019-06-12 6:42 ` [Buildroot] [PATCH 2/4] package: remove 'v' prefix from tarball-fetched packages Victor Huesca
2019-06-19 21:06 ` Arnout Vandecappelle
2019-06-20 6:13 ` Thomas Petazzoni
2019-06-20 9:23 ` Victor Huesca
2019-06-20 19:43 ` Arnout Vandecappelle
2019-06-12 6:42 ` [Buildroot] [PATCH 3/4] package: remove non-conventional prefix/suffix from github-fetched packages Victor Huesca
2019-06-19 21:30 ` Arnout Vandecappelle
2019-06-20 12:42 ` Victor Huesca
2019-06-20 19:50 ` Arnout Vandecappelle
2019-06-21 2:15 ` Carlos Santos
2019-06-12 6:42 ` [Buildroot] [PATCH 4/4] package: remove non-conventional prefix/suffix from tarball-fetched packages Victor Huesca
2019-06-20 21:27 ` Arnout Vandecappelle
2019-06-12 7:26 ` [Buildroot] [PATCH 0/4] Sanetize packages version Thomas Petazzoni
2019-06-12 8:39 ` Victor Huesca
2019-06-12 14:50 ` Thomas Petazzoni
2019-06-19 15:35 ` Victor Huesca
2019-06-20 20:32 ` Arnout Vandecappelle
2019-06-23 16:33 ` Thomas Petazzoni
2019-06-12 8:51 ` Arnout Vandecappelle
2019-06-18 12:11 ` Victor Huesca
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=20190620083110.4986e5fa@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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