[aur-general] Doubt conflict array & request check PKGBUILDS
morganamilo at gmail.com
Wed Oct 16 20:47:54 UTC 2019
On Wed, 16 Oct 2019 at 21:22, Iyán Méndez Veiga <me at iyanmv.com> wrote:
> I recently adopted two packages from AUR: adwaita-qt and adwaita-qt4. Today
> @morealaz (who is maintaining adwaita-qt-git) asked me to edit some of the
> arrays in the PKGBUILD (please read comments in the AUR website) and after
> reading the wiki I did a commit with those little changes.
> I am not sure if they are correct and he argues that I should a conflict array.
> Can someone have a look at these two (three) PKGBUILDS and tell me if I should
> change something and why?
replaces=(foo) is for when a package is replaced. Pacman will
foo during the next upgrade and replace it with your package. Not the
that's suitable for packages that *can* be used as an alternative.
With conflicts=(foo), it's the job of a package to conflict with what
(if they do conflict) and not the other way around. For example
foo-git provides and
conflicts with foo. But foo has no reason to conflict with foo-git
because the conflict has
already been stated in the other package.
So if your changes follow those rules then you're good.
More information about the aur-general