Magnus Therning
Oh, don't get me wrong, some parts are already perfect. The kind of things I was thinking of was
• modify cabal2arch to accept the location of the local copy of the ABS tree so that the new PKGBUILD is created in the correct place • modify cabal2arch to be aware of the layout of the ABS tree (especially I expect that we would want some way of separating binary and source packages) • modify cabal2arch in the directions that Don has already pointed out, i.e. to remove the static, compiled-in lists (e.g. naming of C packages for dependencies), instead those lists should be kept outside the binary (maybe even make it possible to get them from a URL)
I am strongly bothered by the fact that the PkgBuild "Show" function is implemented in cabal2arch and not in the archlinux module, is there anybody against merging them together ? -- Rémy.