[aur-requests] [PRQ#11784] Deletion Request for minecraft
mkolassa [1] filed a deletion request for minecraft [2]: While I understand that this package was created first (by several years), it has not been updated to use the new version or even the new path mentioned by the developer (https://twitter.com/Dinnerbone/status/981978843178323968) even after several comments from users. Because of this, I would like to flag this for deletion in lieu of minecraft-launcher (https://aur.archlinux.org/packages/minecraft-launcher). [1] https://aur.archlinux.org/account/mkolassa/ [2] https://aur.archlinux.org/pkgbase/minecraft/
Ok, 2 things: 1. The URL on the official website, today, still points to http://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.jar , if the new launcher is the "official" one why are they not updating that link? This package will continue to point to this URL 2. The tweet mentioned do not talk about the download link, but about the version file and my package already points to the link requested by Dinnerbone: https://aur.archlinux.org/cgit/aur.git/tree/minecraft?h=minecraft#n11 Please stop making those flagging and requests, thank you. Christophe Robin *Independent Contractor* *IT Consulting* *Nekoo K.K.* On Tue, Jun 12, 2018 at 7:16 AM, <notify@aur.archlinux.org> wrote:
mkolassa [1] filed a deletion request for minecraft [2]:
While I understand that this package was created first (by several years), it has not been updated to use the new version or even the new path mentioned by the developer (https://twitter.com/Dinnerbone/status/981978843178323968) even after several comments from users. Because of this, I would like to flag this for deletion in lieu of minecraft-launcher (https://aur.archlinux.org/packages/minecraft-launcher).
[1] https://aur.archlinux.org/account/mkolassa/ [2] https://aur.archlinux.org/pkgbase/minecraft/
Request #11784 has been rejected by Eschwartz [1]: This package is the canonical correct name, and if it is not updated then it should be orphaned, not deleted. HOWEVER, the other package is a beta package, and just because the beta package is commonly used does not mean it intrinsically should be the primary version. People who explicitly want the beta are welcome to install the other package; meanwhile, people who prefer the stable release should not have this package deleted... It's needlessly confusing IMHO because the other package should be called minecraft-beta, not minecraft-launcher. If Mojang could clarify whether the beta is actually stable, then this package could be updated -- it's not being held back because of lack of maintainer interest, but due to the judgment call of the maintainer who feels that updating would be incorrect. tl;dr Betas are not stable releases and vice versa. These are different packages. [1] https://aur.archlinux.org/account/Eschwartz/
participants (2)
-
Christophe Robin
-
notify＠aur.archlinux.org