You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cabal2arch (the binary) tries to load two files, ghc-provides.txt and library-providers.txt. These two files are installed by archlinux (the package). This means that the PKGBUILD for cabal2arch can't makedepend on archlinux but instead has to depend on it. In other words, since archlinux contain data files the basic assumption that executables only need to makedepend on all libraries is wrong for executables that use archlinux.
I think there are two solutions to this:
Move the two data files to cabal2arch, that's where the function for loading them is so that's where they belong.
Remove the data files from archlinux completely and make cabal2arch always load them from a URL. (Or at least make it load them from a URL by default, this might make more sense from a developer and testing perspective.)
I would prefer the second solution.
The text was updated successfully, but these errors were encountered:
I should probably add that the two solutions are specific to cabal2arch. In the long run we need to address the more general problem of libraries having datafiles.
As a quick-fix, I've uploaded a new version of cabal2arch to AUR and kiwilight.com that declares a run-time dependency on haskell-archlinux. The PKGBUILD was hand-edited, though, so this is really a hack.
cabal2arch
(the binary) tries to load two files,ghc-provides.txt
andlibrary-providers.txt
. These two files are installed by archlinux (the package). This means that thePKGBUILD
for cabal2arch can'tmakedepend
on archlinux but instead has todepend
on it. In other words, since archlinux contain data files the basic assumption that executables only need tomakedepend
on all libraries is wrong for executables that use archlinux.I think there are two solutions to this:
cabal2arch
always load them from a URL. (Or at least make it load them from a URL by default, this might make more sense from a developer and testing perspective.)I would prefer the second solution.
The text was updated successfully, but these errors were encountered: