https://wiki.haskell.org/index.php?title=HaskellImplementorsWorkshop/2012/Schuster&feed=atom&action=historyHaskellImplementorsWorkshop/2012/Schuster - Revision history2015-08-02T18:29:42ZRevision history for this page on the wikiMediaWiki 1.19.14+dfsg-1https://wiki.haskell.org/index.php?title=HaskellImplementorsWorkshop/2012/Schuster&diff=55061&oldid=prevHenk-Jan van Tuyl: Added Category:Community2012-12-17T13:43:29Z<p>Added Category:Community</p>
<table class='diff diff-contentalign-left'>
<tr valign='top'>
<td colspan='1' style="background-color: white; color:black;">← Older revision</td>
<td colspan='1' style="background-color: white; color:black;">Revision as of 13:43, 17 December 2012</td>
</tr></table>Henk-Jan van Tuylhttps://wiki.haskell.org/index.php?title=HaskellImplementorsWorkshop/2012/Schuster&diff=46894&oldid=prevGregoryCollins: New page: =Making cabal-install non-destructive= ''Philipp Schuster (speaker), Andres Löh'' Recently there have been more and more complaints about "cabal dependency hell". Many of these complai...2012-07-18T09:05:08Z<p>New page: =Making cabal-install non-destructive= &#039;&#039;Philipp Schuster (speaker), Andres Löh&#039;&#039; Recently there have been more and more complaints about &quot;cabal dependency hell&quot;. Many of these complai...</p>
<p><b>New page</b></p><div>=Making cabal-install non-destructive=<br />
<br />
''Philipp Schuster (speaker), Andres Löh''<br />
<br />
<br />
Recently there have been more and more complaints about &quot;cabal<br />
dependency hell&quot;. Many of these complaints have their root in one<br />
limitation: It is not possible to have more than one instance of a<br />
certain package version installed per package database. Installing<br />
another instance overwrites the existing instance and often breaks<br />
other installed packages that depended on the overwritten instance.<br />
<br />
During a Summer of Code project we are lifting this restriction by<br />
making several instances of the same package version install next to<br />
each other. This requires serious changes to ghc-pkg, cabal-install,<br />
the Cabal library and their interaction. Specifically we need:<br />
<br />
* A unique install location for each instance<br />
* An improved way to uniquely identify packages<br />
* A refined adhoc resolution method for GHC<br />
* A few changes to the cabal-install solver<br />
* A garbage collection mechanism for unused packages<br />
<br />
In this talk, we are going to describe the changes as well as the<br />
improvements possible for the end user. In addition to removing the<br />
possibility of breaking installed packages, the new system also<br />
promises much more fine-grained dependency tracking.<br />
<br />
The project is a work in progress, and the talk will be a status<br />
report.</div>GregoryCollins