Peter Verswyvelen bugf...@gmail.com writes:
I don't think it is realistic to expect that for a project of medium to
large size that you work only with stable versions of modules (this would
exclude most packages on Hackage I guess).
I think you're putting too much into stable here. IMO,
On 29 Mar 2009, at 22:26, Xiao-Yong Jin wrote:
Peter Verswyvelen bugf...@gmail.com writes:
Mmm, my email was indeed very unclear about my question.
A very simple example: suppose a development team is working on a
program.
This program consist of modules A and B. Each module has it's own
On Mon, Mar 30, 2009 at 8:33 AM, Ketil Malde ke...@malde.org wrote:
Do one thing, and do it well. File versioning and change history:
darcs. Dependency tracking and building: cabal.
Yes, that could actually work. I would just need some link between a cabal
version and Darcs version (I must
Mmm, my email was indeed very unclear about my question.
A very simple example: suppose a development team is working on a program.
This program consist of modules A and B. Each module has it's own Darcs
repository.
Module A requires B. When a new developer wants to get the source code, he
does a
Peter Verswyvelen bugf...@gmail.com wrote:
To me, any version control system should be able to track dependencies
between repositories. Something similar like Cabal's dependency
system.
So my question is really, how do you solve the dependency tracking
between several Darcs repositories?
On Sun, 29 Mar 2009, Peter Verswyvelen wrote:
Module A requires B. When a new developer wants to get the source code, he
does a darcs get server://program/A, which gives him only the latest
version of A. So he manually needs to do darcs get server://program/B
(that B is required is usually
On Sun, Mar 29, 2009 at 10:04 PM, Ganesh Sittampalam gan...@earth.liwrote:
There's an (unimplemented) proposal by David Roundy for darcs sub-repos
that would solve this problem: you have a darcs patch type that means
depend on this patch from this other darcs repo which will be checked out
in
Peter Verswyvelen bugf...@gmail.com writes:
Mmm, my email was indeed very unclear about my question.
A very simple example: suppose a development team is working on a program.
This program consist of modules A and B. Each module has it's own Darcs
repository.
Module A requires B. When a
On 2009 Mar 29, at 16:26, Xiao-Yong Jin wrote:
Peter Verswyvelen bugf...@gmail.com writes:
Module A requires B. When a new developer wants to get the source
code, he
does a darcs get server://program/A, which gives him only the
latest version
of A. So he manually needs to do darcs get
On Sun, Mar 29, 2009 at 10:26 PM, Xiao-Yong Jin xj2...@columbia.edu wrote:
Now assume you don't have 2 modules but dozens...
I can't imagine such kind of situation, unless you are
really working on a very big project. Usually, if your
project depends on other projects, mostly it should
I assume cabal install darcs isn't what you're looking for.. can you
give a real-world example ?
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
11 matches
Mail list logo
