[kepler-dev] Build Script - Checking out Ptolemy

[Sivaramakrishnan, Chandrika]

Matt, Christopher, David,

Thank you for the updates. I agree with Matt and Christopher. Since most of Kepler users don't update ptolemy, it would be useful to make  https the default. Probably even better if there is a flag to specify which source to use. That way the flag can be set by the ptII developers

Thanks
Chandrika
-----Original Message-----
From: David Welker [mailto:david.v.welker at gmail.com] 
Sent: Thursday, April 29, 2010 2:14 PM
To: Christopher Brooks
Cc: Sivaramakrishnan, Chandrika; kepler-dev at ecoinformatics.org
Subject: Re: [kepler-dev] Build Script - Checking out Ptolemy

Hi Chandrika,

The reason that svn is used instead of https or svn+ssh is because these latter two protocols were causing problems.

We may look at these issues again post 2.0.

-David


On Apr 29, 2010, at 2:20 PM, Christopher Brooks wrote:

> Hi Chandrika
>
> See 
> http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/2009-June/01
> 4880.html
>
> Checking out https is more likely to work than using svn or svn+ssh, 
> so I'm all for it.
>
> One issue is that when users check out the ptII repository using 
> svn://, then they are not likely to able to update the ptII 
> repository.
>
> To update ptII repository, users should check out ptII using svn
> +ssh://.
> A few users (primarily sponsors) can write the ptII repository via 
> https.
>
> However, many sites seem to be blocking https svn traffic.  svn also 
> needs to be configured, see
>
> http://chess.eecs.berkeley.edu/ptexternal/wiki/Main/Subversion#Firewal
> lAndProxy
>
> It would be nice if it was easy to configure the build system to use 
> https or svn+ssh to check out the repository.
>
> The fact that authorized users are not able to write the ptII 
> repository using https is largely artificial, but not likely to 
> change.
>
>
> _Christopher
>
>
>
>
>
>
> On 4/29/10 12:44 PM, Sivaramakrishnan, Chandrika wrote:
>> Hi,
>> Kepler build script downloads ptolemy from 
>> svn://source.eecs.berkeley.edu. This is not accessible to people like 
>> me who are behind firewall. I always have to check out ptolemy 
>> manually using _https://source.eecs.berkeley.edu/svn/_ path. Even 
>> after I do that, even ant update hangs when trying to update ptolemy.
>> If everyone with or without a firewall can access the https url, 
>> could the build script be updated to use https instead of svn?
>> Thanks
>> Chandrika
>>
>>
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>
> -- 
> Christopher Brooks, PMP                       University of California
> CHESS Executive Director                      US Mail: 337 Cory Hall
> Programmer/Analyst CHESS/Ptolemy/Trust        Berkeley, CA 94720-1774
> ph: 510.643.9841 fax:510.642.2718	      (Office: 545Q Cory)
> home: (F-Tu) 707.665.0131 cell: 707.332.0670 
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev