[darcs-users] darcs patch: Import relevant bits of gorsvet, for now... (and 16 more)

Petr Rockai me at mornfall.net
Fri May 29 11:15:35 UTC 2009


Hi,

Eric Kow <kowey at darcs.net> writes:
> Ah! Yes, as you probably noticed I got confused reading the cabal list
> hashed-storage output.  How strongly do you feel about build slaves
> working?
Well, I'd be unhappy to lose them, although they are in a somewhat disorganised
state, AFAICT.

> In any case, if I apply this right now (I intend to apply just the
> Darcs.Gorsvet patch before it gets reviewed since it's non-invasive),
> the slaves are going to break.
(See below -- please wait at least till hashed-storage is on hackage and the
build depends are sorted properly.)

> Do you want me to wait for you to upload a copy of hashed-storage
> onto hackage so that build slave owners can just cabal install
> hashed-storage?  Or would you rather I gave instructions to darcs
> get hashed storage?  Or something else?
Hmm. Hard question, actually. My sort of preliminary plan is to branch
hashed-storage about now, creating branches for 0.3.x and 0.4 -- for 0.3.x
keeping the current functionality as it is, and 0.4 for work on a new pristine
format (as outlined in the SoC project). So it would make sense to release 0.3
to hackage, make the dependency say >= 0.3 && < 0.4 and push any further fixes
through hackage (possibly bumping the dependency to >= 0.3.1 and so on).

Can you think of anything major that will be needed for darcs 2.3 in
hashed-storage? The whitespace issue is now fixed (in hashed-storage), so the
only thing I can think of is endianity, so the binary index is platform
independent (although it should be pretty safe either way, since the index
would automatically fix itself on first use).

As for the API, that's still in flux, but I don't expect that to be an
issue. Any invasive changes will happen on the 0.4 branch.

Yours,
   Petr.

-- 
Peter Rockai | me()mornfall!net | prockai()redhat!com
 http://blog.mornfall.net | http://web.mornfall.net

"In My Egotistical Opinion, most people's C programs should be
 indented six feet downward and covered with dirt."
     -- Blair P. Houghton on the subject of C program indentation


More information about the darcs-users mailing list