| Starting from a fresh tree everytime or searching for files manually
| don't sound realistic
>Perhaps the easiest thing is to start with a fresh link-tree.
>That's easy and fast -- but does not work on Windows.
So your recommendation for me is to 'darcs get;darcs-all
get --extra' every time I want to 'pull' & 'make' on windows?
Surely a *local* darcs get is pretty cheap? And it will certainly leave
you with an entirely clean tree in which to start a build.
Well, even the initial 'darcs get' of 20k ghc patches isn't
exactly fast (and then it fails with unapplicable patch, just as
darcs check does? I'm pretty sure that used to work locally
at least with darcs 1, and a lot faster, too..).
I guess I could try to unlearn my aversion and use the terminally
broken 'darcs get --partial', but then I'd have to remember not
to do anything darcsish in that copy. So, I'd have one full copy
to use darcs in and one partial copy to build in. And another copy
to validate in. And another copy for keeping my local changes in.
And keep all copies in synch, not forgetting sub-repos. Yes,
sounds great. Not.
What is wrong with a proper 'make', cleaning, dependencies,
and all, at least as an aim, if not yet in practice? Of course, you
can move house every time your dirty plates fill your sink, so that
you have an entirely clean house in which to start the week, but
that isn't more than a workaround, not a solution.
Yep, darcs1 just finished getting where darcs2 failed. Time
for another bug report..
Claus
_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
