tag:blogger.com,1999:blog-8768401356830813531.post3245363211447893989..comments2023-01-12T13:01:39.386-05:00Comments on Software Simply: Using Cabal With Large Projectsmightybytehttp://www.blogger.com/profile/15198998578494149797noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8768401356830813531.post-62972793529494493772013-02-05T15:45:26.822-05:002013-02-05T15:45:26.822-05:00> creates a link to the package
Will this feat...> creates a link to the package<br /><br />Will this feature support remote repositores, like cabal-meta does (I guess not)?Dmitry Dzhusnoreply@blogger.comtag:blogger.com,1999:blog-8768401356830813531.post-84384290156580074242012-11-08T11:00:15.141-05:002012-11-08T11:00:15.141-05:00The new cabal sandboxing will support both the use...The new cabal sandboxing will support both the use cases of cabal-dev and of cabal-meta. We've implemented a concept called package environments, which is general enough to implement both sandboxing and adding more than on source directory to a build. More concretely you would do:<br /><br />cabal sandbox init<br />cabal sandbox add-source ../xmlhtml<br />cabal sandbox add-source ../heist<br />cabal sandbox add-source ../snap-core<br />cabal sandbox add-source ../snap-server<br /><br />Note that this add-source, unlike cabal-dev's, creates a link to the package, so it gets rebuilt properly if it changes.<br /><br />The package environment also lets you lock down specific version constraints for packages.Johan Tibellhttps://www.blogger.com/profile/06875432206357419172noreply@blogger.com