[kepler-dev] Build Script - Checking out Ptolemy
David Welker
david.v.welker at gmail.com
Thu Apr 29 14:38:38 PDT 2010
Oh, I was confused by these phrase:
> Switching the default build to use ptolemy's svn over https
I see, you prefer to use https. I read this as you thinking that svn
made more sense. That svn refers to both the repository and to the
protocol can be confusing.
The reason we do not use https now is because it caused the build to
fail because of interactive certification queries that the build was
not able to handle gracefully. Apparently, when we use https on our
repository, the same issues do not arise. Perhaps there is a solution
such as a command-line option that will suppress such interactive
certification queries or a change in how the Ptolemy SVN is configured
so that it behaves in the same manner as the Kepler SVN where these
issues to not arise.
Anyway, we can look at this post 2.0. I just wanted to clarify my
confusion over Matt's preferences.
-David
On Apr 29, 2010, at 3:13 PM, Matt Jones wrote:
> Switching the default build to use ptolemy's svn over https makes
> sense to me, as it will help most developers who only need a read-
> only copy of the ptolemy module to build, and avoids firewall issues
> that block ssh ports. For those few Kepler developers who have
> write access to ptII, I think they can easily set up a separate svn
> +ssh checkout to make their changes.
>
> I prefer that this change happens after the 2.0 release, as we don't
> want to delay that.
>
> Matt
>
> On Thu, Apr 29, 2010 at 12:20 PM, Christopher Brooks <cxh at eecs.berkeley.edu
> > wrote:
> Hi Chandrika
>
> See http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/2009-June/014880.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#FirewallAndProxy
>
> 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
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100429/93b608ca/attachment.html>
More information about the Kepler-dev
mailing list