Re: Changing package file extension

[Jordi Gutiérrez Hermoso]

2009/1/29 John W. Eaton <address@hidden>:
> On 29-Jan-2009, Jordi Gutiérrez Hermoso wrote:
>
> | 2009/1/27 John W. Eaton <address@hidden>:
> | > Is anyone willing to do the work to make the change?  Should we
> | > support both the new extension (whatever it is we choose) and the old
> | > tar.gz?
> |
> | So what exactly needs to be changed? I looked at the pkg.m script, and
> | the actual extension isn't used anywhere except in the docstrings...
> | Just change those?
> |
> | It would be nice if "pkg add <TAB>" would try to autocomplete with
> | .octpkg extension... does the parser need a modification for this to
> | happen?
>
> If the extension is not explicitly used in pkg.m, then I guess it is
> just a matter of documentation and changing the names of the Octave
> Forge packages.

Is this really all that has to be done? It feels kinda silly to submit
a diff for something like this. I guess the real change has to be in
the 'Forge website.

- Jordi G. H.

diff -r 4d90d21a9cd9 scripts/pkg/pkg.m
--- a/scripts/pkg/pkg.m Thu Jan 29 11:49:06 2009 +0100
+++ b/scripts/pkg/pkg.m Thu Jan 29 14:01:00 2009 -0600
@@ -26,10 +26,10 @@
 ## @item install
 ## Install named packages.  For example,
 ## @example
-## pkg install image-1.0.0.tar.gz
+## pkg install image-1.0.0.octpkg
 ## @end example
 ## @noindent
-## installs the package found in the file @code{image-1.0.0.tar.gz}.
+## installs the package found in the file @code{image-1.0.0.octpkg}.
 ##
 ## The @var{option} variable can contain options that affect the manner
 ## in which a package is installed. These options can be one or more of
@@ -184,7 +184,7 @@
 ## @code{pkg}. The form of the command to build a binary package is
 ##
 ## @example
-## pkg build builddir image-1.0.0.tar.gz @dots{}
+## pkg build builddir image-1.0.0.octpkg @dots{}
 ## @end example
 ##
 ## @noindent