From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] pkg-stats: more upstream names
Date: Wed, 5 Feb 2020 18:13:02 +0100 [thread overview]
Message-ID: <20200205181302.59a1099e@windsurf> (raw)
In-Reply-To: <20190828070251.22886-2-francois.perrad@gadz.org>
On Wed, 28 Aug 2019 09:02:51 +0200
Francois Perrad <fperrad@gmail.com> wrote:
> the python infrastructure populates the variables _NAME_UPSTREAM
> (like the luarocks one).
> and pkg-stats uses them.
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/pkg-python.mk | 1 +
> support/scripts/pkg-stats | 7 ++++++-
> 2 files changed, 7 insertions(+), 1 deletion(-)
So we discussed this with Arnout, and since release-monitoring.org
provides this mapping functionality, and someone has already filled in
the mapping details for almost all Buildroot packages. We don't want to
duplicate that information in Buildroot itself.
However, we can improve a bit the logic in pkg-stats when querying by
"guess". I'll reply to your PATCH 1/2 with more details about this idea.
In the mean time, I've marked this particular patch as Rejected.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-05 17:13 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 [this message]
2019-08-28 12:43 ` [Buildroot] [PATCH 1/2] pkg-stats: query release-monitoring.org with upstream name Thomas Petazzoni
2019-09-01 7:46 ` 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=20200205181302.59a1099e@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