FS#67653 - [reflector] provide pacman-mirrorlist

Attached to Project: Community Packages
Opened by Philipp Klein (kleinph) - Thursday, 20 August 2020, 19:16 GMT
Last edited by Xyne (Xyne) - Tuesday, 20 October 2020, 18:41 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Xyne (Xyne)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Make reflector package provide pacman-mirrorlist, so that the mirrorlist package can be uninstalled and doesn't generate a .pacnew file on update.
It would be also consistent, as reflector actually provides an mirrorlist file.
This task depends upon

Closed by  Xyne (Xyne)
Tuesday, 20 October 2020, 18:41 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Use e.g. https://aur.archlinux.org/packages/refle ctor-nomirrorlist/
Comment by Xyne (Xyne) - Friday, 21 August 2020, 02:11 GMT
The package doesn't actually provide a mirrorlist. The user can configure it to generate one, but that is entirely optional. Without user intervention, the package would not satisfy the dependency so I am reluctant to implement this.
Comment by Philipp Klein (kleinph) - Friday, 21 August 2020, 15:19 GMT
This point of view makes somehow sense. I don't know what the official stance on this is.

Also a provides field allows both packages to coexist, so removing pacman-mirrorlist would be optional.
Comment by Erich Eckner (deepthought) - Sunday, 11 October 2020, 17:35 GMT
While I see Xyne's point, I think, in most (if not all) cases, reflector is installed to provide the mirrorlist. In cases, where this is not intended (because reflector is used to create a mirrorlist for a different purpose than the host itself), one can still opt to keep pacman-mirrorlist installed.
If you want to keep the dependency-tree clean in such cases, you can add pacman-mirrorlist as an optdepends to reflector (I'm not sure, what description should be put there, though). Then, one can keep pacman-mirrorlist installed and it will not be considered a leaf-package.
Comment by Xyne (Xyne) - Sunday, 18 October 2020, 23:05 GMT
I'll bring this issue up on the mailing list to see what the devs think.
Comment by Xyne (Xyne) - Tuesday, 20 October 2020, 18:41 GMT
After a brief discussion on arch-dev-public, I've decided to leave the package as-is. The desired behavior can be achieved using a a custom dummy package, e.g. https://aur.archlinux.org/packages/reflector-nomirrorlist/

Closing.

Loading...