I've forgot to send a copy of my reply to the list.Here it is. 2008/6/5 Brad Nicholes <[EMAIL PROTECTED]>: >>>> On 6/5/2008 at 4:16 AM, in message > <[EMAIL PROTECTED]>, "Kuba Konczyk" > <[EMAIL PROTECTED]> 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 >> ;) > > > So is the convert-to-package.sh script something that should be run whenever > >the package is being built or should the results of this conversion be > something >that we commit to the SVN repository permanently. IOW, should the > >gmetad-python sub-directory be laid out differently in order to support the > python >package build.If so then just let me know how this directory should > be laid out >and we can make the changes in the SVN repository. If you run the script, that's it.Script is only necessary for conversion and not for an actual build. >Then I am assuming that we just need to add the setup.py.in file and apply the >>configure.in patch. Is this correct? Yes it is. > > Brad > > -- Kuba
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
