If I were involved in the development of cabal (the tool) then I'd be
resisting the slippery slope towards becoming a general package
manager. The line should be drawn somewhere, and I personally think
that cabal (the tool) should _only_ be concerned with building Haskell
packages, if a Haskell package depends on a C library then that
library has to be installed prior to the invocation of cabal (the
tool), and in a manner that fits the user's system (e.g. using apt-get
on Debian).
Just my 2p...
/M
On Fri, Jun 5, 2009 at 12:53 AM, Maurício
Hi,
I just submitted bindings to libusb, and realized I should comment pkgconfig-depends in .cabal since libusb-1.0 is not installed on the server, or cabal would refuse building it.
There are many libraries we probably would like to have bindings for, but we need to have them on hackage to do that. What if we generate a wish list of really trusted and important libraries we would like to use, and then test if they build on hackage, and install in /usr/local those that do?
I have a few sugestions:
http://www.gnu.org/software/gsl
http://directory.fsf.org/project/mailutils
Best, Maurício
_______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries
-- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe