Allow configuring mirrorlist per architecture & repo #135
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vieter-v/vieter#135
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
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.
Allow configuring mirrorlist per architectureto Allow configuring mirrorlist per architecture & repoPackages 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.