Need advice on how to address possible conflict with former (no longer existing) AUR package
I published my first ever AUR package: https://aur.archlinux.org/packages/polyglot-git As per the submission guidelines, I made sure that neither `polyglot` nor `polyglot-git` currently exist in any official repositories or the AUR. Upon publishing my package, I saw that it is listed as optionally required by four other AUR packages, including this one (due to listing `polyglot` as provided in the PKGBUILD): https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=polyglot-winboard-git The package `polyglot` no longer exists, but its PKGBUILD is still available: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=polyglot As things stand, those four packages will automatically pull in the one I just published as a dependency for no good reason. I'm asking for advice as to which actions it would be most proper to take at this point.
Hello, In order to deal with conflicts you should add the following fields to your PKGBUILD: provides=('polyglot') conflicts=('polyglot') This will give the user a prompt that the packages are in conflict, and will ask them to remove polyglot if it is installed, allowing them to install the VCS version. You can also add other conflicts if needed. Hope this helps, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev
The problem is not that there's an alternative version, it's that there's a totally different package with the same provides On 2023/9/12 6:57, Polarian wrote:
Hello,
In order to deal with conflicts you should add the following fields to your PKGBUILD:
provides=('polyglot') conflicts=('polyglot')
This will give the user a prompt that the packages are in conflict, and will ask them to remove polyglot if it is installed, allowing them to install the VCS version.
You can also add other conflicts if needed.
Hope this helps,
Hello, Sorry I misunderstood then. I suggest the following: If the package is the same upstream was the other package, they are duplicates and thus you should just use the former. If the package are two different upstreams, hence different projects, you will need to append something to the name. Lone_Wolf appears to have given a suggestion for this anyways. I apologise for the misunderstanding. Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev
On 12-09-2023 09:10, Ildar Sagdejev wrote:
As things stand, those four packages will automatically pull in the one I just published as a dependency for no good reason.
They won't do that. Optional dependencies are never installed without explicit orders . It does look like there are 2 softwares called ployglot : http://hgm.nubati.net/cgi-bin/gitweb.cgi?p=polyglot.git;a=summary and yours at https://github.com/specious/polyglot The other one doesn't appear to have had commits after 2016,, so it's easy to overlook it. Maybe you could switch to another name like polyglot-translate ? Lone_Wolf
participants (4)
-
Aaron Liu
-
Ildar Sagdejev
-
Lone_Wolf
-
Polarian