clyde icon indicating copy to clipboard operation
clyde copied to clipboard
verified publisher icon Kiwi

AUR conflicts don't inform until after build

Open splondike opened this issue 15 years ago • 3 comments

When downloading a package from AUR which conflicts with an installed package, clyde doesn't inform of the conflict until after everything is downloaded and built. Normal packages (from the repos) do raise this issue before downloading.

Conflicting examples in AUR: 'opera' and 'opera-devel'. Conflicting examples in normal packages: 'fam' and 'gamin'.

splondike avatar Apr 21 '10 12:04 splondike

There is no way to know what files are contained in an AUR package until it is built. No database of files for each AUR package is available, unlike repository packages. Unfortunately this has no practical solution and I am closing the issue.

juster avatar Jul 30 '10 19:07 juster

I don't think that's what I meant, I would like clyde to parse the 'conflicts' array prior to building the package, see http://wiki.archlinux.org/index.php/PKGBUILD . The opera-devel package for example has "conflicts=('opera' 'opera-beta')".

splondike avatar Jul 31 '10 03:07 splondike

Oh I see you are taking about the conflicts array not conflicting files. My mistake.

juster avatar Jul 31 '10 07:07 juster