On Mon, Jan 31, 2022 at 11:55:07PM +1000, Allan McRae via arch-dev-public wrote:
On 31/1/22 23:23, David Runge via arch-dev-public wrote:
Hi all,
given recent topics for build automation and work on internal projects I would like to announce a code walkthrough for arch-repo-management [1].
I would like to give an overview of the scope of the project, its current features and which features I would like to see implemented (some of which are still in a discussion phase). I will try to add a few more tickets beforehand to track open features and to outline them better. This way I hope that it becomes easier for interested people to follow up on them.
The meeting will take place on Jitsi https://meet.jit.si/20220202-arch-repo-management
on 2022-02-02 starting around 19:00 CET (UTC+01:00).
Any changes to the date and/or location will be announced in this mail thread.
Best, David
[1] https://gitlab.archlinux.org/archlinux/arch-repo-management/
Any chance this can be recorded? It will be at 4am in my timezone?
I am interested in mainly what problem this is solving. From what I can tell, our current workflow is package->db, and this goes package->json->db. What is the advantage of the extra step? Will this be covered by your talk?
It would be in python which is more maintainable then the juggle of bash we curently have. JSON would also provide us with a machine readable format which is usefull for us in extending tooling in the future. The JSON document would also replace the repository state that is kept in our svn mono-repository, so it solves a few more issues with the git migration. https://wiki.archlinux.org/title/User:Foxboron/GitMigration You can see a plaintext space seperated version of this in this mock up which we decided on a couple of years ago when we discussed git. -- Morten Linderud PGP: 9C02FF419FECBE16