Hi, For a while I have been thinking cabal-install should really be a library. Has anyone considered or thought about this? I am wondering how much work it may be? Best wishes, Jens
Why not call out to cabal-install as a sub-process?
Best,
Leon
On Wed, Dec 24, 2014 at 10:54 PM, Jens Petersen
Hi,
For a while I have been thinking cabal-install should really be a library. Has anyone considered or thought about this? I am wondering how much work it may be?
Best wishes,
Jens
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
Hi Jens,
Can you explain what you mean, or how would you use it?
E.g do you mean having the cabal commands as functions, into which you can
pass a directory structure (with file contents included) as data types?
On Dec 25, 2014 4:54 AM, "Jens Petersen"
Hi,
For a while I have been thinking cabal-install should really be a library. Has anyone considered or thought about this? I am wondering how much work it may be?
Best wishes,
Jens
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
Sorry Carl I missed your reply...
On 3 January 2015 at 02:03, Carl Eyeinsky
Can you explain what you mean, or how would you use it?
E.g do you mean having the cabal commands as functions, into which you can pass a directory structure (with file contents included) as data types?
Pretty much yes. Since I believe the code is well written, my feeling is it might not be a huge amount of work though I haven't had time to look into the details. The hardest part might be working out the name of the library unless cabal-install becomes a BinLib package. ;o) I think there are quite a few packages that make use of cabal-install and so yes better and safer to have a library then having always to call out to a subprocess... Jens
Hi Jens,
I think there are quite a few packages that make use of cabal-install and so yes better and safer to have a library then having always to call out to a subprocess...
If you're using a subprocess, then you're always using the same, the installed cabal-install version. With a cabal-install library, your application might use an other version of cabal-install than the installed cabal-install binary and this might result into issues. Also if it seems counterintuitive, the best solution might be to have a library that usese a subprocess ;). Greetings, Daniel
participants (4)
-
Carl Eyeinsky -
Daniel Trstenjak -
Jens Petersen -
Leon Smith