From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] pkg-stats: query release-monitoring.org with upstream name
Date: Wed, 28 Aug 2019 14:43:52 +0200 [thread overview]
Message-ID: <20190828144352.239a231d@windsurf.home> (raw)
In-Reply-To: <20190828070251.22886-1-francois.perrad@gadz.org>
Hello,
+Victor Huesca in Cc.
On Wed, 28 Aug 2019 09:02:50 +0200
Francois Perrad <fperrad@gmail.com> wrote:
> By default, this upstream name is our BR name.
> But with perl-package infrastructure, the variables *_DISTNAME
> give the CPAN name which is known by release-monitoring.org
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
Thanks for implementing this. It matches what we discussed. The only
possible issue that I can see is if a package defines FOO_DISTNAME for
some internal reason, but is not a perl-package. Then we will pick up
whatever DISTNAME contains.
Perhaps we should standardize on FOO_NAME_UPSTREAM for all package
infrastructures including perl-package, and make it a "reserved"
variable name, so that it is forbidden to use it for anything else ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-28 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:02 [Buildroot] [PATCH 1/2] pkg-stats: query release-monitoring.org with upstream name Francois Perrad
2019-08-28 7:02 ` [Buildroot] [PATCH 2/2] pkg-stats: more upstream names Francois Perrad
2019-08-28 12:46 ` Thomas Petazzoni
2019-09-01 7:46 ` François Perrad
2020-02-05 17:13 ` Thomas Petazzoni
2019-08-28 12:43 ` Thomas Petazzoni [this message]
2019-09-01 7:46 ` [Buildroot] [PATCH 1/2] pkg-stats: query release-monitoring.org with upstream name François Perrad
2020-02-05 17:17 ` Thomas Petazzoni
2020-02-07 16:58 ` François Perrad
2020-02-12 9:22 ` Thomas Petazzoni
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=20190828144352.239a231d@windsurf.home \
--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 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.