Derek,
In the meantime, I found a way to repackage the existing AG2.3 .deb and
change the dependencies without a complete rebuild - the new version ran
OK with wxgtk2.6, as we need it to, but it couldn't connect to any
venues i.e. useless.
However I was able to use the same technique to use an existing AG2.4
package (built for another Linux distribution) to construct a new AG2.4
.deb package. This works properly and it more or less works together
with a new AG3 package I have in progress. There are some kinks (not
bugs) still to be ironed out before I can release them, but I can't work
on that for a few days i.e. they should be available sometime this
coming week.
BTW, to properly deinstall the AG2.3 package, the packages:
accessgrid2.3
wxgtk2.4
should be libwxgtk2.4
wxgtk2.4-python
should be libwxgtk2.4-python
globusdatamanaggcc32gcc32dbgpthr3.0.2
should all be removed. Then, AG3 can be installed (with better
features anyway)
Until the new packages are ready, you could still try the existing AG3
package if you properly deinstall your AG2.3 package (as above - note
corrections). You can always reinstall the AG2.3 package if you need to,
but you may find the facilities in AG3 too good to want to go back :)
chris
Christoph Willing +61 7 3365 8350
QCIF Access Grid Manager
University of Queensland