[PRQ#43592] Deletion Request for vte-git
msnspk [1] filed a deletion request for vte-git [2]: Duplicates the vte3-git and vte4-git packages already found in the AUR. Maintainer seems to be using these packages to harass other maintainers [1] https://aur.archlinux.org/account/msnspk/ [2] https://aur.archlinux.org/pkgbase/vte-git/
On Tue, Jul 4, 2023 at 11:53 PM <notify@aur.archlinux.org> wrote:
msnspk [1] filed a deletion request for vte-git [2]:
Duplicates the vte3-git and vte4-git packages already found in the AUR. Maintainer seems to be using these packages to harass other maintainers
[1] https://aur.archlinux.org/account/msnspk/ [2] https://aur.archlinux.org/pkgbase/vte-git/
Ignoring the silly conflict between the maintainers of aur/vte{3,4}-git and aur/vte-git, it seems to me that this request is incorrect. In the normal Arch Linux package, the vte-common vte3 vte4 vte-docs are actually split packages from the same PKGBUILD. They are not different PKGBUILDs like aur/vte{3,4}-git. The ideal solution would be: - Update the vte-git PKGBUILD, to have the split packages vte-common-git vte3-git vte4-git vte-docs-git. There is should be no such package as vte-git, that's only the pkgbase. - Delete vte3-git vte4-git, with a deletion request. The technical issue would be the temporary name conflict between the split package and PKGBUILD versions of vte{3,4}-git. I am not sure how the AUR software handles that, and a TU should clarify.
Request #43592 has been Rejected by fabiscafe [1]: While the vte-git packages are dups of vte3-git and vte4-git, they have a good purpose of trying to stay in line with the Arch way. A deletion would be the wrong impulse. All 3 pkgbases (vte-git, vte3-git, vte4-git) should be merged instead. [1] https://aur.archlinux.org/account/fabiscafe/
participants (2)
-
eNV25
-
notify@aur.archlinux.org