Forwarding as I think my reply to "aur-requests" will not be actually delivered:
Actually I leave this to the "Arch staff" to decide.
Yes, you are right that this was created to "work around" issues in some AUR helpers and I did not know that this issue no longer exists.
And as updating this dummy package is a separate step that was never automated I tend to forget to push version numbers there. So I would also prefer to have this package gone.
Maybe the "decision makers" know better about the current situation about AUR helpers. I, myself, don't use any AUR helpers at all.
If it is no longer needed, then please delete "vdr-api" and tell me so I can delete on the vdr4arch GitHub project, too.
Manuel
On 10.04.22 02:07, notify@aur.archlinux.org wrote:
MarsSeed [1] filed a deletion request for vdr-api [2]:
This dummy package is not useful and not required.
It was created to accommodate some AUR helpers that lack such a basic and necessary feature as handling the provides entries on AUR during dependency resolution.
(I am using yay and paru, both handle them well.)
This package was created for AUR/vdr. That package now has a versioned provides - currently this: provides = vdr-api=2.6.1
This package, vdr-api, was not kept up to date with the above, as it currently has pkgver=2.4.7
Yet, dependents requiring vdr-api=2.6.1 can be installed just fine by paru and yay, because AUR/vdr provides exactly that. No need for this (outdated) intermediary dummy package.
Example dependent that I tried and which installs fine without even requiring AUR/vdr-api: https://aur.archlinux.org/packages/vdr-play
Safe to delete, as its now incorrect version proves my point. No users have complained that they couldn't install dependents of AUR/vdr because of a version mismatch. Guess they use a proper AUR helper like paru or yay or something on par with them, and their tool of choice was able to resolve the dependency correctly without AUR/vdr-api as a dummy intermediary.
[1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/vdr-api/
On Sun, 10 Apr 2022 13:31:16 +0200 Manuel Reimer via aur-general aur-general@lists.archlinux.org wrote:
Forwarding as I think my reply to "aur-requests" will not be actually delivered:
Actually I leave this to the "Arch staff" to decide.
Yes, you are right that this was created to "work around" issues in some AUR helpers and I did not know that this issue no longer exists.
And as updating this dummy package is a separate step that was never automated I tend to forget to push version numbers there. So I would also prefer to have this package gone.
Maybe the "decision makers" know better about the current situation about AUR helpers. I, myself, don't use any AUR helpers at all.
If it is no longer needed, then please delete "vdr-api" and tell me so I can delete on the vdr4arch GitHub project, too.
The deletion request is highly misleading because it gives the impression that "yay", "paru" or "proper AUR helpers" are legimitate concerns for AUR maintainers when writing their packages. They are not.
The only tool that a PKGBUILD should be compatible to is makepkg (and optionally, makechrootpkg, as this catches some issues makepkg might not and is the build tool for packages in the official repositories).
As such this package can safely be removed, but hardly for what is outlined in the deletion request.
Alad
Manuel
On 10.04.22 02:07, notify@aur.archlinux.org wrote:
MarsSeed [1] filed a deletion request for vdr-api [2]:
This dummy package is not useful and not required.
It was created to accommodate some AUR helpers that lack such a basic and necessary feature as handling the provides entries on AUR during dependency resolution.
(I am using yay and paru, both handle them well.)
This package was created for AUR/vdr. That package now has a versioned provides - currently this: provides = vdr-api=2.6.1
This package, vdr-api, was not kept up to date with the above, as it currently has pkgver=2.4.7
Yet, dependents requiring vdr-api=2.6.1 can be installed just fine by paru and yay, because AUR/vdr provides exactly that. No need for this (outdated) intermediary dummy package.
Example dependent that I tried and which installs fine without even requiring AUR/vdr-api: https://aur.archlinux.org/packages/vdr-play
Safe to delete, as its now incorrect version proves my point. No users have complained that they couldn't install dependents of AUR/vdr because of a version mismatch. Guess they use a proper AUR helper like paru or yay or something on par with them, and their tool of choice was able to resolve the dependency correctly without AUR/vdr-api as a dummy intermediary.
[1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/vdr-api/
aur-general@lists.archlinux.org