Allow configuring mirrorlist per architecture & repo #135

Open
opened 2022-04-21 13:54:10 +02:00 by Jef Roosens · 1 comment

We could add the ability to configure the mirrorlist that the builder image uses, with some decent provided defaults. This could speed up builds on servers that happen to be far away from the default mirrors. It would also users to e.g. use the same mirrors as their desktop/laptop systems, ensuring their builds stay in sync with their systems.

This would maybe require the builder image to be built from scratch each time, but I don't actually think this would think that long. Additionally, allowing to configure the build step for the base image would be useful.

This setting could then also be used to add custom repositories to a build.

We could add the ability to configure the mirrorlist that the builder image uses, with some decent provided defaults. This could speed up builds on servers that happen to be far away from the default mirrors. It would also users to e.g. use the same mirrors as their desktop/laptop systems, ensuring their builds stay in sync with their systems. This would maybe require the builder image to be built from scratch each time, but I don't actually think this would think that long. Additionally, allowing to configure the build step for the base image would be useful. This setting could then also be used to add custom repositories to a build.
Jef Roosens added this to the 0.4.0 milestone 2022-04-21 13:54:10 +02:00
Jef Roosens added the
enhancement
label 2022-04-21 13:54:10 +02:00
Jef Roosens changed title from Allow configuring mirrorlist per architecture to Allow configuring mirrorlist per architecture & repo 2022-05-23 16:30:23 +02:00

Packages within a specific arch-repository should be built with the same list of mirrors enabled. This way, they couldn't be out of sync with each other.

Packages within a specific arch-repository should be built with the same list of mirrors enabled. This way, they couldn't be out of sync with each other.
Jef Roosens modified the milestone from 0.4.0 to 0.6.0 2022-06-17 09:33:48 +02:00
Jef Roosens removed this from the 0.6.0 milestone 2022-12-29 10:18:43 +01:00
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#135
There is no content yet.