Since I am helping with a university course myself at the moment, I want to add that the work-around described in the second linked cabal issue (#6515), namely setting `store-dir` and `remote-repo-cache` to a global read-only location, works very well in practice. In my opinion, it achieves its goals easily: * Reduce storage (everyone uses the same index and packages) * Easy to synchronize (you can install additional versions for all students) * Easy to maintain (new semester? Just remove the store folder and build every package anew) And for the easier `ghci` workflow, a generated ghci environment file is also really handy and easy to upgrade/change. Best regards, Fendor On 3/21/21 6:55 PM, Johannes Waldmann wrote:
.. a few people mention that they prefer the "global package database" style. I'd like to improve my understanding of why people prefer that style. Teaching.
Reduce storage, and save students the extra work and distraction. https://github.com/haskell/cabal/issues/7172
same question, with discussion of possible work-around with "shared local" database: https://github.com/haskell/cabal/issues/6515
I will need this in two week's time ..
- J.W. _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.