Alberto G. Corona | 11 May 11:10 2013
Picon

I wish cabal-dev to travel back in time

Hi Café:

 

I created just now an issue in cabal-dev:

 

https://github.com/creswick/cabal-dev/issues/101

 

When compiling old developments, I wish cabal-dev to install and build dependencies that were available at a that time

I don't know if  there are alternatives to solving this issue. I think that this is very useful and necessary, specially now when library updates are increasingly frequent.

Maybe this problem is already solved and I just don´t know (as is often the case, for example when, in a sudden aha moment, I reinvented cabal-install months after the release). That is the reason why I tell you about it here in order to discuss it.

motivation:

I´m installing now an old soft development. Since many of my dependencies were labeled with -any or with > , neither I neither cabal know which library versions are the right ones. By taking into account a date parameter, cabal-dev can figure out which libraries were the latest and the right ones at that time.
--
Alberto.

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe <at> haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Simon Hengel | 11 May 11:25 2013
Picon

Re: I wish cabal-dev to travel back in time

Personally I think we need something akin to Ruby's `Gemfile.lock`
mechanism (ideally directly integrated into Cabal).

Cheers,
Simon

On Sat, May 11, 2013 at 11:10:45AM +0200, Alberto G. Corona  wrote:
> Hi Café:
> 
> 
> 
> I created just now an issue in cabal-dev:
> 
> 
> 
> https://github.com/creswick/cabal-dev/issues/101
> 
> 
> 
> When compiling old developments, I wish cabal-dev to install and build
> dependencies that were available at a that time
> 
> I don't know if  there are alternatives to solving this issue. I think that
> this is very useful and necessary, specially now when library updates are
> increasingly frequent.
> 
> Maybe this problem is already solved and I just don´t know (as is often the
> case, for example when, in a sudden aha moment, I reinvented cabal-install
> months after the release). That is the reason why I tell you about it here
> in order to discuss it.
> 
> motivation:
> 
> I´m installing now an old soft development. Since many of my dependencies
> were labeled with -any or with > , neither I neither cabal know which
> library versions are the right ones. By taking into account a date
> parameter, cabal-dev can figure out which libraries were the latest and the
> right ones at that time.
> -- 
> Alberto.

> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe <at> haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
Bardur Arantsson | 11 May 18:24 2013
Picon

Re: I wish cabal-dev to travel back in time

On 05/11/2013 11:10 AM, Alberto G. Corona wrote:
> Hi Café:
> 
> 
> 
> I created just now an issue in cabal-dev:
> 
> 
> 
> https://github.com/creswick/cabal-dev/issues/101
> 
> 
> 
> When compiling old developments, I wish cabal-dev to install and build
> dependencies that were available at a that time
> 
> I don't know if  there are alternatives to solving this issue. I think that
> this is very useful and necessary, specially now when library updates are
> increasingly frequent.
> 
> Maybe this problem is already solved and I just don´t know (as is often the
> case, for example when, in a sudden aha moment, I reinvented cabal-install
> months after the release). That is the reason why I tell you about it here
> in order to discuss it.
> 

This is an issue that the JVM ecosystem is struggling with as well. I'd
encourage people who are thinking about implementing something to have a
look at

   https://github.com/sbt/adept/wiki/NEScala-Proposal

and especially the linked video.

Gmane