I think the better option here would be to enforce this in the cabal file. (i.e. set `cabal-version: >=1.20`)
At the moment we have `cabal-version: >=1.8`, which is way too low. Peter Harpending On Sat, May 23, 2015 at 05:36:06PM -0700, Aaron Wolf wrote: > Another Vagrant question: Cabal wasn't updated on the Vagrant box. It's > all the way back at 1.18. I believe we care about having at least 1.20 > and 1.22 is working overall. The Debian instructions get people 1.22 > > Should we add instructions for running cabal update and cabal install > cabal-install? Or can we simply update the Vagrant thing to have updated > Cabal already? > > On 05/23/2015 04:13 PM, Aaron Wolf wrote: > > So, the SETUP_DEBIAN.md has the commands that set the $PATH so that > > `sdm` on its own works. In the SETUP_VAGRANT.md there is no setting of > > the path. I just merged Denver's commit that used the longer address for > > sdm so that the Vagrant instructions actually work. But it would be > > preferable to have the path set, I think. > > > > So, for those who know Vagrant, can we just run the same commands as in > > SETUP_DEBIAN? Any other issues? > > > > On a side note, just wondering: is there any way to have Vagrant be > > available with pre-built sdm or otherwise pre-built full sandbox? Or > > would that mean excessive need to constantly update Vagrant? Or maybe > > things need rebuilding enough anyway that it isn't worthwhile? > > > > > > -- > Aaron Wolf Snowdrift.coop <https://snowdrift.coop> > _______________________________________________ > Dev mailing list > [email protected] > http://lists.snowdrift.coop/mailman/listinfo/dev
pgpG8wfE_9K7j.pgp
Description: PGP signature
_______________________________________________ Dev mailing list [email protected] http://lists.snowdrift.coop/mailman/listinfo/dev
