It's not too late to add it, but that doesn't necessarily mean it's going to make it in either.
I'm assuming ./setup.py sdist was to be run in the qpid/tools directory? The artifact produced by doing that has no LICENCE, NOTICE, or (as ./setup.py complains about) README files. The first two are required and the last would appear necessary to tell you what to do with these files once you have them, as e.g. the archive doesn't include the Python client (which is fair enough, but needs documented for those that don't know its required), and aren't there also other files required for general QMF functionality, or are those included with the python client? The file listing seems a little light: qpid-tools-0.8/ qpid-tools-0.8/src/ qpid-tools-0.8/src/py/ qpid-tools-0.8/src/py/qpid-route qpid-tools-0.8/src/py/qpid-tool qpid-tools-0.8/src/py/qpid-cluster qpid-tools-0.8/src/py/qpid-config qpid-tools-0.8/src/py/qpid-cluster-store qpid-tools-0.8/src/py/qpid-stat qpid-tools-0.8/src/py/qpid-queue-stats qpid-tools-0.8/src/py/qpid-printevents qpid-tools-0.8/setup.py qpid-tools-0.8/PKG-INFO If someone who knows what bits are needed / where they are / how to use them etc wants to make some updates on trunk to produce a useful artifact for the management tools then I would be happy to include that in the next RC. I intend to produce RC3 tomorrow night (Monday 22nd), from about 9pm GMT. If someone wants to take a shot at this could you either do so before then or let us all know that you are going to imminently and I will hold off until it's ready, otherwise I would suggest it will just have to wait for the next release. Robbie > -----Original Message----- > From: Jonathan Robie [mailto:jonathan.ro...@redhat.com] > Sent: 19 November 2010 19:06 > To: dev@qpid.apache.org > Subject: Re: qpid-config and 0.8 client distributions > > On 11/19/2010 01:49 PM, Gordon Sim wrote: > > On 11/19/2010 03:03 PM, Jonathan Robie wrote: > >> Should the 0.8 client distributions include qpid-config, qpid-tool, > etc? > > > > No, I don't think so. However I do think they should be available as > a > > separate artifact. All that requires is running ./setup.py sdist. > > OK, I agree that's better. > > > Is it too late to add that to the list of artifacts for the next RC? > > I hope it's not too late ... > > Jonathan > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
