Here's a quick spot check qpid-0.8.tar.gz. Three things we might want to
change ...
File: qpid-0.8.tar.gz
###./qpid-0.8 directory:
No README.txt or INSTALL in the top-level directory. The user needs an
overview that describes which directories contain which component, and
points to README.txt and INSTALL in those directories.
Where do I start if I want to build a client in a given language or a
given broker?
### ./qpid-0.8/cpp directory:
README.txt contains a "Quick Start" that doesn't work, because there is
no configure file:
3. Quick start
==============
If you are impatient to get on, ./configure && make will usually be
sufficient to compile. Running make check will run tests, make install
will install the client and daemon. For more detailed information,
please see the INSTALL notes.
We do ship configure with the cpp distribution.
### ./qpid-0.8/cpp/examples directory:
Do we want to continue to ship the old API examples, with no indication
that these are using the older API? I would remove them or at least put
them in a subdirectory with a name that indicates they do not use the
current API.
Jonathan
P.S. In the ./cpp directory, the build succeeds, and 'make check' does
not return any errors. I did this on a box that does not have clustering
installed.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
