Re: changing pkg function to use new packages.octave.org subdomain

[Rik]

On 01/19/2013 10:00 AM, address@hidden wrote:
> Message: 3
> Date: Fri, 18 Jan 2013 16:54:48 -0500
> From: "John W. Eaton" <address@hidden>
> To: octave maintainers mailing list <address@hidden>
> Cc: address@hidden
> Subject: changing pkg function to use new packages.octave.org
>       subdomain
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I checked in the following changes so that the pkg function now looks to 
> packages.octave.org instead of octave.sourceforge.net.  For now, we are 
> rewriting the URLs to point to source forge, but in the future we may do 
> something else.  By using packages.octave.org and rewrite rules now, we 
> should be able to make a transition more easily in the future, without 
> having to change pkg.m.
>
> http://hg.savannah.gnu.org/hgweb/octave/rev/7ad3eea8a3af
>
> I made the change on stable so that it will appear in the upcoming 3.6.4 
> release and we might be able to make a change in the location of Octave 
> Forge packages sooner than we would if the change only goes on the 
> default branch.  I don't think this is a particularly risky change, but 
> if anyone strongly disagrees, let me know.  I've also merged the changes 
> to default.
We can update section D.1, Contributing Guidelines, to mention that
octave-maintainers is now a shared list for Octave core and Octave Forge
package discussions.  I think we can get rid of Git as a build requirement
in D.2 as well.

--Rik