On Wed, 2009-06-24 at 15:05 +0200, Petr Rockai wrote:
> Hi!
>
> I'd like to announce immediate availability of a first beta release of darcs
> 2.3. There is a number of improvements and bugfixes over the last stable
> release (2.2). Moreover, work has been done on performance of "darcs whatsnew"
> for large repositories. This has also introduced a slight risk of regressions,
> but please note that all of the disruptive changes are in read-only code
> paths: the new code will never touch your repository, so it is unable to cause
> permanent harm. The worst that could happen is that you get no or bad diff
> from
> "darcs whatsnew". (This is also a reason why we need your testing!)
The good news is that darcs gzcrcs --check/--repair seems to be working
fine.
A few comments I have after installing:
Configuring HTTP-3001.1.5...
Preprocessing library HTTP-3001.1.5...
Building HTTP-3001.1.5...
Why are we using HTTP-300x.x in new releases? In cabal-install-0.6.2 we
switched over to HTTP-4000.x and it's great. HTTP-4000.x is used in the
current Haskell Platform releases. It's faster and handles proxies
better. I am aware that there are still some issues but I'm not aware of
any regressions compared to the 300x series. The actual code changes to
update to the new API are minimal. Are there particular reasons for
sticking with the older versions?
Building mmap-0.2...
[1 of 1] Compiling System.IO.MMap ( System/IO/MMap.hs,
dist/build/System/IO/MMap.o )
cbits/posix.c: In function ‘system_io_mmap_file_open’:
cbits/posix.c:33:0:
warning: cast to pointer from integer of different size
cbits/posix.c: In function ‘system_io_mmap_file_close’:
(and 5 others similarly)
This makes me very nervous. This is on Linux x86-64. Can someone look
into that and fix it?
Duncan
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
