Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add functionality to deal with missing dependencies in CABAL files #22

magthe opened this Issue Jan 11, 2011 · 0 comments


None yet
1 participant

magthe commented Jan 11, 2011

We have two issues, #14 and #16, relating to CABAL files missing dependencies. A recent version of hogre had a similar problem (though it's been fixed upstream in a newer version). Basically some upstream devs opt to discover libraries and tools at configuration time and they then leave the dependency out of the CABAL file. I don't think we'll see this practice end, and while it in these three examples is possible to use the CABAL file there may very well be occasions when configuration time discovery is the only viable option.

To deal with this we ought to add functionality to cabal2arch to deal with this. Some sort of mapping file springs to mind, but there may very well be better ways of doing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment