getting complete HEAD repo, darcs issues
Claus Reinke
claus.reinke at talk21.com
Wed Nov 21 09:12:34 EST 2007
i've finally bitten the bullet and am changing from a partial
to a complete HEAD repo. that hasn't solved as many
issues as i'd hoped, though:
1 could the tar-balls at darcs.haskell.org please be split
according to repo-collection? that is, one each for
ghc, corelibs, testsuite, extralibs
i fetched the ghc-corelibs.tar.bz2 version, but
testsuite doesn't like 'darcs get --complete', either;
currently, i'd have to fetch all of the rest again just
to get the testsuite, right? that would block my slow
line for hours, again.
2 i'm trying to recreate my old setup, where i had
- one full repo (with extralibs, with my unrecorded
changes), updated from the main HEAD repo,
for creating binary dists that i actually use, and
for recording patches to send here
- a secondary repo, updated from my local repo,
with only the bits needed for validate
but now, when i try to do 'darcs get --partial' from
my new complete local repo, it seems to want to
get all patches, which fails, of course. does that
mean that checkpoints are local to a repo, not
recorded? how do i list checkpoints in a repo?
should i create my own checkpoints, or would
that interfere with patches i send?
3 which reminds me: darcs-all gets in the way when
working from local repos on windows:
- absolute paths on windows start with a
drive letter, so /^\// will not match
- protocols should be matched explicitly,
just matching for /:/ will erroneously
capture full windows paths
4 the first thing i tried when i finally had a complete
repo was 'darcs annotate', which always failed
in partial repos, i think. but it still fails, now with
a stack overflow, after a long time..
should there be a ghc ticket collecting all the
outstanding darcs issues/darcs workarounds/
darcs tickets relevant to ghc developers?
claus
More information about the Cvs-ghc
mailing list