From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Notifications about outdated packages
Date: Tue, 27 Aug 2019 11:23:59 +0200 [thread overview]
Message-ID: <20190827112359.38e154ae@windsurf.home> (raw)
In-Reply-To: <CAB0FRssnr8UrMQB1J51FY9VJnWNedjctQmnuD7J61y0w=PfJ-g@mail.gmail.com>
Hello Fran?ois,
Thanks for your feedback!
On Sat, 17 Aug 2019 20:03:12 +0200
Fran?ois Perrad <francois.perrad@gadz.org> wrote:
> release-monitoring.org has a CPAN backend.
> We have currently 110 packages using the perl/cpan infrastructure.
> The current http://autobuild.buildroot.net/stats/ shows 4 packages found by
> `distro`, others are in the status 'Not found'.
>
> I think that 110 packages could be found by `guess`, because with the
> perl/cpan infrastructure, we have the distribution name.
> For example, with perl-foo-bar:
> PERL_FOO_BAR_NAME=perl-foo-bar
> PERL_FOO_BAR_DISTNAME=Foo-Bar (used by the target perl-foo-bar-upgrade)
>
> So, the search must use *_DISTNAME instead of *_NAME
This indeed seems to work for a number of packages.
> Note: the luarocks infrastructure supplies an equivalent which is named
> *_NAME_UPSTREAM.
I've tried with a few luarocks packages, and it didn't give any useful
results with release-monitoring.org.
But for the Perl case, what we could do is:
- pkg-stats extracts the DIST_NAME variable (it already extracts
VERSION, LICENSE and LICENSE_FILES), and store it in some "upstream
name" member of the Package class.
- pkg-stats then uses this "upstream name" if available when querying
release-monitoring.org.
Fran?ois, since Victor is about to finish his internship (end of this
week), he won't have the time to work on this. Do you want to work on
it and propose a patch ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-08-27 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 10:18 [Buildroot] Notifications about outdated packages Thomas Petazzoni
2019-08-17 18:03 ` François Perrad
2019-08-27 9:23 ` Thomas Petazzoni [this message]
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=20190827112359.38e154ae@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox