[AG-TECH] Problems while installing AGkt2.2 from source on a Debian

[Joseph]

Hi all

I apologise for the delay of this answer. Yesterday was the Queens 
Birthday and so a public holiday. Moreover, I have been working on 
installing a AG2.2 from the binary for someone here who needed AG2.2 
quicly, so I didn't do a lot recently. I have requested a new certificat 
and everything seems to work. Wait and see.

However, I've a good new : I have build AG2.2 from the source on a another 
machine and the errors from crypto and pyOpenSSL have disappeard. However, 
I don't understand why exactly since I installed the same packages as on 
the other pc, so... I have attached the "usual" info4.tar to this mail if 
never someone wants to have a closer look.

I'm also really pleased to see that someone is working closer on the 
debian packaging. So I will answer to David as far as I can and then ask a 
few question.

<snip>
> The gpt.sh file sets GPT_LOCATION (these's something similar for
> GLOBUS_LOCATION), a mandatory environment variable - unfortunately,
> mandatory env vars are usually not allowed in official debian packages,
> packages are supposed to have "sensible defaults" e.g.
> /usr/lib/globus or /usr/lib/gpt. Packaging globus is by far the most
> problematic part if you ask me, and I have heard nothing further about
> the debian intent-to-package it, so I think we can assume
> it's up to us.

I agree. As I think this package won't be register as one official (ie 
availabled from Debian), we can do this kind of stuff.

> I am still just trying to work my way through the debian policy manual
> and new maintainers guide (see debian site - I assume you've seen them
> if you're looking at debian packaging), so I am no authority on these
> things.

I do the same so I'm neither an authority on these things.

> The following is all IMHO:

My answers and comments are too IMHO.

> Looking at the 2.2 bundle with a view to producing a debian
> source package or packages:
>
>>>>>> Drop
> Optik
> Logging
> No need to include these, they're in python 2.3

I agree.

>>>>>> Packaged for debian
> I think this is unmodified in the AG bundle, so safe to use debian
> version (?)
> openssl

I used the debian version without trouble for the time, so...

>
>>>>>> Separate packaging
> gt3.0.2-source-installer        Now at version 3.2 "pre-WS".
> I that it might be appropriate to separate out globus packaging.  But
> maybe not.

I was thinking of doing a separate package for globus-AG, as they have 
done a separated rpm for it. However I'm not sure of the interest of doing 
so.

I also wonder what would be the consequence of an already installed globus 
(with differents bundles and configuration). It could lead to a conflict I 
think. Any clue someone ?

>>>>>> AG-Specific sources:

I'm more at ease for the time with the idea of producing a accessgrid-2.2 
binary package. A source package could be interesting too but a binary one 
would be, I think, easier, at least to start with. With binary we wouldn't 
have to bother with all the other softwares required for the building of 
AccessGrid and so it should be easier. I was just thinking of doing that 
for the time, what do you think of this ?

Thanks for your interest and help !

Cheers,
     Joseph
-------------- next part --------------
A non-text attachment was scrubbed...
Name: info4.tar
Type: application/x-tar
Size: 593920 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/ag-tech/attachments/20040615/17c12c1b/attachment.tar>