AG 2.3 Packaging

[Ivan R. Judson]

> I think a release is premature right now if its to be based 
> on the current CVS.

Ut oh. Let's see what we can do :-)
 
> As I mentioned at the Townhall meeting, I've been having 
> trouble making a fully working package for a while now - the 
> beta2 release, in fact.
> I've been busy on other things to look into it, but this 
> email about a release has me worried enough to start.
> 
> Here are problems I've found so far:
> 
> 1. bin/AGNodeService.py is missing from the CVS 

It's been removed in favor of using AGServiceManager.py -n (which runs the
node service)

> 2. packaging/linux/BuildPackage.py still refers to 
> SOAPpy-0.11.4, whereas packaging/BuildPythonModules.py regers 
> to SOAPpy-0.11.5 

This is Tom's call. 0.11.5 is officially out, but Tom didn't want to move to
it for Gentoo, since we'd have to build a package for it.

> 3. after manualy adjusting the above and 
> trying a build, a request for win32.Config ???
> followed by a long list of import errors:
> 
> 
> DEBUG:VenueServer:VenueServer initializing authorization manager.
> Importing 110 modules.
>   [  0%] ....................................

Epydoc errors are not worrisome. Annoying but not worrisome. To fix it means
requires re-arranging the order of the build and making sure the PYTHONPATH
is set to the dist dir. This was being done correctly previously, but
someone (to rename nameless :-), commented out the epydoc because it took
too long. Now we need to make sure it works again, or not include
autogenerated docs. This doesn't affect the operation of the toolkit
however.

> and it just gets worse from there on. At the end of it all 
> (ignoring all the errors, a package is built but it doesn't 
> do anything usefull. For instance running certmgr.py gives:
> 
> Traceback (most recent call last):
>   File "/usr/bin/certmgr.py", line 29, in ?
>     from AccessGrid.Toolkit import CmdlineApplication
>   File 
> "/mnt/scratch/AG2.3/AccessGrid-2.3_beta2/dist-20040910_194317/
> lib/python2.3/site-packages/AccessGrid/Toolkit.py", line 22, in ?
>     from AccessGrid.Security import CertificateManager
>   File 
> "/mnt/scratch/AG2.3/AccessGrid-2.3_beta2/dist-20040910_194317/
> lib/python2.3/site-packages/AccessGrid/Security/CertificateMan
> ager.py", line 49, in ?
>     from AccessGrid import Utilities
>   File 
> "/mnt/scratch/AG2.3/AccessGrid-2.3_beta2/dist-20040910_194317/
> lib/python2.3/site-packages/AccessGrid/Utilities.py", line 32, in ?
>     from AccessGrid import Platform
>   File 
> "/mnt/scratch/AG2.3/AccessGrid-2.3_beta2/dist-20040910_194317/
> lib/python2.3/site-packages/AccessGrid/Platform/__init__.py", 
> line 55, in ?
>     from AccessGrid.Platform.unix import Config as Config
>   File 
> "/mnt/scratch/AG2.3/AccessGrid-2.3_beta2/dist-20040910_194317/
> lib/python2.3/site-packages/AccessGrid/Platform/unix/Config.py
> ", line 25, in ?
>     from pyGlobus import security
> ImportError: No module named pyGlobus
> 

These are worrisome. But I can't tell what's actually happening from them.
Can you send the full list?

> Has anyone succeeded in producing a working package recently?

I have a windows package -- I've been buildling, installing, fixing,
committing and rebuilding the package most of the week. The mac package is
in a different state -- it's probably going to be late, since we're just
learning how to package for it :-)

--Ivan