Re: [Ganglia-developers] gmetad-python installation/packaging

[Brad N. <BNI...@no...>]

   Thanks, build and install is one of the major "todo" items for gmetad-python.  I will take a look at this and get it committed.  

There are also a number of other cleanup and testing items left to do.  One of the major clean up items is to refactor the dataStore and Element classes so that they are more self contained.  IOW, so that the other classes and functionality don't have to know so much about the internals of the dataStore and Element classes in order to use them (ie. the xml writer functionality that produces the XML output).  Anybody who wants to dive in and start tying up all of the loose ends in gmetad-python, is certainly welcome.

Brad

>>> On 6/5/2008 at 4:16 AM, in message
<2e9...@ma...>, "Kuba Konczyk"
<jak...@gm...> wrote:
> Hi Guys,
> 
> I've modified gmetad-python to use a python packaging convention and
> also created python setuptools script.
> The point is to be able to install gmetad-python using 'python
> setup.py install' and with some more work use
> setuptools packaging capabilities (creating source package,
> RPM).Former currently works fine, latter doesn't.
> 
> Attached is a simple script (convert-to-package.sh) that should be run
> in gmetad-python directory.It'll create Gmetad package, move necessary
> files into it, rename them appropriately and adjust every source file
> to use the new package.
> Next you should copy 'setup.py.in' script into gmetad-python
> directory and apply 'configure.in.patch' (both attached).Then run
> './bootstrap' and './configure' which will generate
> gmetad-python/setup.py.Finally in gmetad-python run 'python setup.py
> install'.I've tested it on a linux with a fresh ganglia trunk.
> 
> Meta data in setup.py is far from been complete/correct, but it's
> trivial to extend/change it later on.
> 
> During the file name conversion, gmetad_random.py was renamed to
> random.py which is using random module from the standard library.This
> has created name conflict (random.py would try to import itself), so
> I've renamed it again to grandom.py which might not be the best pick
> ;)