Date: 2001-10-30 14:14:09
(starting new thread from "Report from Redmond")
i said regarding threads:
> > ah, yes, i now see it is in 1_25 (in fact its test directory takes
> > more than 1Mbyte by itself...)
> Huh? The test directory has 2 files, Jamfile at < 1KB and
> test_thread.cpp at 12KB. That's a max of 13KB which is a far sight
> from 1MB. In fact, the entire boost\libs\thread directory tree
> only 314KB including CVS cruft (so the release in Zip format should
> be even smaller).
all i know is that as i type this, http://www.boost.org/boost_all.zip
is 4.3mB as a zip file, expanding to over 12mB, and that the
top pigs are such things as:
-rwxr-xr-x 114815 Oct 1 14:14 test_thread.exe
-rw-r--r-- 236804 Oct 1 14:14 test_thread.ilk
-rw-r--r-- 211142 Oct 1 14:14 test_thread.obj
-rw-r--r-- 476160 Oct 1 14:14 test_thread.pdb
it would be nice if:
1. a release were identical to a snapshot of the CVS at some time,
sans the CVS cruft, without someone's personal build artifacts.
2. the release history were documented, with a date, scm label,
human-generated release notes, and (ideally) automatically generated
3. someone documented whether tar.gz and .zip releases are identical,
or line endings are different
4. the hosted documentation files on boost.org showed a version id
5. the hosted documentation and source files matched the latest cvs.
(For example, http://www.boost.org/boost/array.hpp pointed to from
http://www.boost.org/libs/array/index.htm does not match cvs of
even several months ago.)
right now, afaik, none of those are true.
-mda, releasing some pent-up annoyance (sorry)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk