I think anything required that isnt already easily available in another archive needs to be included in the new tools archive. E.g. downloading the full-release archive to extract 'qpid/extras/qmf' would obviously be a bit much given it has 50+MB of other stuff in it, but making people download the standalone python client archive which is required in full wouldnt be too bad.
Robbie On 22 November 2010 14:36, Jonathan Robie <jonathan.ro...@redhat.com> wrote: > Running these requires the QMF bits (qpid/extras/qmf) and the Python client. > What's the best way to handle these dependencies? > > Jonathan > > On 11/21/2010 02:15 PM, Robbie Gemmell wrote: >> >> 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 > > --------------------------------------------------------------------- > 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
