I'm having the following issue with Guix from AUR: Guix requires
gnutls to be built with Guile bindings. The maintainers of the official
gnutls package from Arch have apparently opted to explicitly disable Guile bindings when building the package, which is propagated to Manjaro's repositories. Therefore, the
guix package now requires
gnutls-guile, which in turn conflicts with with the official package as both provide
gnutls binaries. This would not be a huge problem by itself, as both packages (atleast at the moment) provide the same version of
gnutls, and any packages requiring
gnutls should work fine with
gnutls-guile. However, because
pamac-common is a
core package and requires
gnutls-guile results in failure if
pamac-common is installed. I've been able to work around this by removing the
gnutls dependency from .PKGINFO and then reinstalling
pamac-common from the modified archive, but this seems less than ideal, as I suspect I'll have to do this every time
pamac-common recieves an update.
So my question goes: Is there a recommended way of handling this type of situation without altering
core packages? If not, what would be an appropriate way to automate this? Perhaps pre-transaction pacman hooks? If so, I'd appreciate some insight into manipulating packages this way, as the
alpm-hooks official documentation seems not to mention anything about it.
Thanks for any and all replies.
P.S. On a completely unrelated note, I've been using the Manjaro i3 community edition for the past year, after a couple of years on Ubuntu (and being exposed to alot of Debian at work). I'm currently running it on 3 separate machines (2 laptops and a home workstation) and I have to say, so far it's been an absolute delight, even when I manage to break it. Big thanks to everyone involved with maintaining Manjaro!