From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Bruno Thomsen <bruno.thomsen@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH] ptxdist: add repology sub command
Date: Sun, 27 Apr 2025 16:58:26 +0200 [thread overview]
Message-ID: <aA5GEqbyBz88MdWK@pengutronix.de> (raw)
In-Reply-To: <CAH+2xPDB0i7YS09kwO1cKMeQryDPH9sOH5D1pqYgFfkNLBiSGA@mail.gmail.com>
On Sat, Apr 26, 2025 at 06:23:35PM +0200, Bruno Thomsen wrote:
> Den lør. 26. apr. 2025 kl. 12.13 skrev Michael Olbrich
> <m.olbrich@pengutronix.de>:
> >
> > On Fri, Apr 18, 2025 at 01:33:57PM +0200, Bruno Thomsen wrote:
> > > Improve ptxdist project visibility by adding it to repology.
> > >
> > > Generate JSON output about all packages in ptxdist for repology.
> > >
> > > ptxdist repology | tail -n +7 | jq
> > >
> > > This is just a POC for integrating ptxdist with repology.
> > >
> > > Add PTXdist support #1487:
> > > https://github.com/repology/repology-updater/issues/1487
> > >
> > > I have run this patch against ptxdist-2024.12.0 and got this output:
> > > https://github.com/baxeno/ptxdist-repology/blob/main/repology.json
> > >
> > > Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> > > ---
> > > Any feedback is welcome as this is a very rough implementation.
> >
> > Hmm, I think it makes more sense to add this to the report stuff in
> > scripts/report/. That should be a pretty simple python script.
> > You can still add a command and make target to call this but there is no
> > need for manual parsing.
>
> Welcome back :)
Thanks, I've been rather busy the last few weeks...
> There is a newer patch version that removes the bash script and does it all
> in makefile. Maybe it should be converted to a python script. This "report"
> is a bit different since it includes all ptxdist packages and not just
> the packages
> used in a project.
No, the report includes all enabled packages. And it includes all
dependencies and for images like the rootfs, all packages that are used to
build the image. With all that information available in one place, it
rather easy to limit what to use.
I've seen the new version and really prefer the Python scripts for that
kind of thing. Ist a lot more flexible. For example I'm pretty sure that
most of the ignore list can by automatically generated by looking at the
package (Does it have a URL?). Doing stuff like that in the Makefile is
painful.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-04-27 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 11:33 Bruno Thomsen
2025-04-19 21:10 ` Ladislav Michl
2025-04-20 8:41 ` Ladislav Michl
2025-04-20 16:18 ` Bruno Thomsen
2025-04-20 18:59 ` Ladislav Michl
2025-04-21 15:51 ` Ladislav Michl
2025-04-26 10:13 ` Michael Olbrich
2025-04-26 16:23 ` Bruno Thomsen
2025-04-27 14:58 ` Michael Olbrich [this message]
2025-04-28 6:24 ` Ladislav Michl
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=aA5GEqbyBz88MdWK@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--cc=ptxdist@pengutronix.de \
/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