search

Kiwi / clyde

Next-generation libalpm/makepkg wrapper.
https://kiwi.github.io/clyde
Other
63 stars 8 forks source link

AUR conflicts don't inform until after build #39

Open splondike opened 14 years ago

splondike commented 14 years ago

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'.

juster commented 14 years ago

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.

splondike commented 14 years ago

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')".

juster commented 14 years ago

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