X-Original-To: alpine-devel@lists.alpinelinux.org Received: from luna.geeknet.cz (luna.geeknet.cz [37.205.9.141]) by lists.alpinelinux.org (Postfix) with ESMTP id 1569A5C4C88 for ; Tue, 20 Jun 2017 16:06:30 +0000 (GMT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luna.geeknet.cz (Postfix) with ESMTPSA id ADDEF76C8F; Tue, 20 Jun 2017 18:06:28 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jirutka.cz; s=mail; t=1497974788; bh=ELkMCwLcsl7uaMjTPA5Ivx3/Dti/tQIYgfFQkBtt2+k=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=IogRwcIk7VBNVq7xN0hGdIErEzY1JyWBz6CCZdz+H0YXKjJPrmx+jUlGp13+n9xK6 5iSQbgvzg1aOXL2PKNQxY8Wu7rhyMGn6rhXUgRo20l3K3K3Rnm3o9FZGYqUi6H93iz PEklVaKaUfck/ABDG00kJu9q4HxmghQ7ii5Ry7uI= Subject: Re: [alpine-devel] Script to parse APKBUILDS and output table of arch support X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_772BB78A-5EF4-4E64-818C-8B16D489BA96" From: Jakub Jirutka X-Priority: 3 In-Reply-To: Date: Tue, 20 Jun 2017 18:06:28 +0200 Cc: alpine-devel@lists.alpinelinux.org Message-Id: <315008DD-D5EB-4369-8A80-F46F10DC528A@jirutka.cz> References: To: Tmp File --Apple-Mail=_772BB78A-5EF4-4E64-818C-8B16D489BA96 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, seding APKBUILDs is not a very good approach how to gather this = information. That said, it can quite work in this case, for =E2=80=9Carch=E2= =80=9D, because this is rarely (if ever) dynamic (e.g. adding archs = based on some conditions) or variously formatted, but not for all = variables. We already have library for sort of programmatic reading of APKBUILDs: = https://github.com/alpinelinux/lua-aports = . It basically just evaluates = every APKBUILD, prints and parsers the selected variables. This is used = e.g. in pkgs.a.o. I agree that such reports would be useful for maintainers for recently = added platforms. However, there are much more reports that would be = useful, so it=E2=80=99d be better to separate data and presentation. I = mean, create a simple RESTful API for aports or just some JSON export, = so anyone can make whatever report needs, without parsing APKBUILDs over = and over again. This is yet another thing on my very long TODO list=E2=80=A6= Hm, maybe this week. It=E2=80=99s pity that we are so dislocated over = the planet, some local hackathons may be very productive for such tasks. = :) Jakub > On 20. Jun 2017, at 16:21, Tmp File wrote: >=20 > Good morning Alpiners. > =20 > I wrote a shell script that reads all APKBUILDS on a repository, = parses the arch=3D setting, and output a csv table with detailed = information about which package is supported by which architecture. > =20 > https://github.com/tmpfile/table > =20 > It outputs a complete table and also a table of only packages that = aren't supported for all archs. > =20 > Here's the final result: = https://github.com/tmpfile/table/blob/master/missing_support_table.csv > =20 > I think this can be of great help to arch maintainers so they can know = with more ease which packages they must work on. > =20 > My goal sharing this work is that someone implements it as a cron job = (for example) on alpinelinux.org/table.html or some other address. > =20 > In the testing I parsed only main/ but it should also work for = community/ and /testing. > =20 > Let me know your opinion. > =20 > tmpfile > =20 > --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: = alpine-devel+help@lists.alpinelinux.org --- --Apple-Mail=_772BB78A-5EF4-4E64-818C-8B16D489BA96 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

seding = APKBUILDs is not a very good approach how to gather this information. = That said, it can quite work in this case, for =E2=80=9Carch=E2=80=9D, = because this is rarely (if ever) dynamic (e.g. adding archs based on = some conditions) or variously formatted, but not for all = variables.

We = already have library for sort of programmatic reading of = APKBUILDs: https://github.com/alpinelinux/lua-aports. It basically = just evaluates every APKBUILD, prints and parsers the selected = variables. This is used e.g. in pkgs.a.o.

I agree that such reports would be = useful for maintainers for recently added platforms. However, there are = much more reports that would be useful, so it=E2=80=99d be better to = separate data and presentation. I mean, create a simple RESTful API for = aports or just some JSON export, so anyone can make whatever report = needs, without parsing APKBUILDs over and over again. This is yet = another thing on my very long TODO list=E2=80=A6 Hm, maybe this week. = It=E2=80=99s pity that we are so dislocated over the planet, some local = hackathons may be very productive for such tasks. :)

Jakub

On 20. Jun 2017, at 16:21, Tmp File <tmpfile@mail.com> = wrote:

Good morning Alpiners.
 
I wrote a shell script that reads all APKBUILDS on a = repository, parses the arch=3D setting, and output a csv table with = detailed information about which package is supported by which = architecture.
 
https://github.com/tmpfile/table
 
It outputs a complete table and also a table of only = packages that aren't supported for all archs.
 
Here's the final result: https://github.com/tmpfile/table/blob/master/missing_support_ta= ble.csv
 
I think this can be of great help to arch maintainers so = they can know with more ease which packages they must work on.
 
My goal sharing this work is that someone implements it = as a cron job (for example) on alpinelinux.org/table.html or some other address.
 
In the testing I parsed only main/ but it should also = work for community/ and /testing.
 
Let me know your opinion.
 
tmpfile
 
--- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---

= --Apple-Mail=_772BB78A-5EF4-4E64-818C-8B16D489BA96-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---