What do think?
We have a
-c all and
-id argument which is used to reset a custom mirrorlist. These arguments will still reset the mirrorlist to use all and every possible mirror.
We have the
-f/--fasttrack argument but that argument returns mirrors which are updated on ALL branches.
Change in the default behavior
so when a user generates a mirrorlist it will use up-to-date mirrors instead of a potentially not updated mirrors. This approach will filter out poorly maintained mirrors such as
belnet.be just to name an example
As is of now pacman-mirrors does not take into account if a mirror is updated for users branch. I am thinking of slight change to pacman-mirrors so when coming to the standard generation of a mirrorlist, pacman-mirrors would filter mirrors based on
- the branch used on the system
- the mirrors sync status
So instead of using all available mirrors which will include mirrors known to be out of sync only mirrors which has an updated syncstatus for the active branch is chosen for the mirrorlist.
Pacman-mirrors knows this due to the download of the status.json from the mirrorservice webpage.
Decided - well almost
--fasttrackargument will be finetuned to take into concideration the users current branch instead of all branches.
Notes in the thinking hat
- What is your take on the
-m random- is it obsolete or what?