You are not logged in.

#1 2018-09-01 20:30:00

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 288

build system

Because this question has been risen a few times, I'd like to present, how our build system works:
package-flow.png
legend:

  • Ellipses are git repositories

  • diamonds are actions

  • hexagons are workers (cron jobs or external machines)

  • rectangles are package repositories, but only the ones in square brackets contain real packages - the others are only entries in our database

The whole thing is automated - in contrast to archlinux which has much more man power.
There is some logic behind "move package" which prevents moving a package if it breaks a dependency.
Likewise, the deletion of a package will be delayed until it does not break any dependency.

Our current problem (python, perl, glibc, qt5) is, that not all dependencies are correctly represented in the database.
We might face similar issues in the future, because archlinux does not support partial upgrades and thus does not need to specify versions in the dependencies at all.

The purpose of this thread is to discuss proposals for improvement and/or questions about the build system.

Regards,
deep42thought

Offline

Board footer

Powered by FluxBB