Re: ncarray 1.0.2 released

[Stephen Montgomery-Smith]

I have similar problems with the name of the directory when creating the 
packages for FreeBSD.  Nan is another example.  But even with the 
others, there is an inconsistency between whether the directory is just 
the name of the package, or the name of the package plus the version number.

If you look at the way I write the FreeBSD ports for octave-forge-*, I 
actually have a variable, called OCTSRC, in the Makefile.  So it isn't a 
big problem for me.  But I can see that it can be annoying.


On 02/19/14 10:26, Orion Poplawski wrote:
> On 02/19/2014 02:13 AM, Alexander Barth wrote:
> > Dear Orion,
> > should I thus in future name the tarball ncArray-x.y.z.tar.gz? (Carnë would
> > this be a problem for the octave-forge site?)
> >
> > The NaN package has also an upcase letter. It uses also an lower case name for
> > the URL:
> >
> > https://downloads.sourceforge.net/project/octave/Octave%20Forge%20Packages/Individual%20Package%20Releases/nan-2.5.9.tar.gz
> >
> > Or did you found that the naming between ncArray and NaN is inconsistent?
> >
> > Thanks and regards,
> > Alex
>
> It may not simply be an issue between the tarball and the directory, but this
> is what I'm seeing while trying to package ncarray for Fedora:
>
> + octave -H -q --no-window-system --no-site-file --eval 'pkg build
> '\''-verbose'\'' /tmp/rpm/octave-ncarray-1.0.2-1.fc20.x86_64
> /export/home/orion/redhat/octave-ncarray-1.0.2/ncArray'
> package name 'ncarray' doesn't correspond to its filename 'ncArray'
> error: called from 'pkg>install' in file /usr/share/octave/3.6.4/m/pkg/pkg.m
> near line 744, column 11
> error: called from:
> error:   /usr/share/octave/3.6.4/m/pkg/pkg.m at line 772, column 5
> error:   /usr/share/octave/3.6.4/m/pkg/pkg.m at line 636, column 3
> error:   /usr/share/octave/3.6.4/m/pkg/pkg.m at line 493, column 7
> error: Bad exit status from /tmp/rpm/rpm-tmp.bIjCCk (%build)
>
> If I rename the directory inside the tarball to "ncarray" from "ncArray" then
> it works.
>
> I get the same error if I try to package it as "ncArray":
>
> + octave -H -q --no-window-system --no-site-file --eval 'pkg build
> '\''-verbose'\'' /tmp/rpm/octave-ncArray-1.0.2-1.fc20.x86_64
> /export/home/orion/redhat/octave-ncArray-1.0.2/ncArray'
> package name 'ncarray' doesn't correspond to its filename 'ncArray'
>
> So the package name of "ncarray" seems to be coming internally from the
> package or octave.
>
> > On Wed, Feb 19, 2014 at 12:27 AM, Orion Poplawski <address@hidden
> > <mailto:address@hidden>> wrote:
> >
> >      On 02/18/2014 03:29 PM, Carnė Draug wrote:
> >      > Hi everyone
> >      >
> >      > a new release of the ncarray package is out, version 1.0.2, by
> >      > Alexander Barth. Enjoy Octave responsibly.
> >      >
> >      > Carnė
> >      >
> >
> >      FWIW - it's annoying packaging this that the package name seems to be 
> > ncArray,
> >      but the tarball name and URL is ncarray.
> >
> >      --
> >      Orion Poplawski
> >      Technical Manager                     303-415-9701 x222
> >      <tel:303-415-9701%20x222>
> >      NWRA, Boulder/CoRA Office             FAX: 303-415-9702 <tel:303-415-9702>
> >      3380 Mitchell Lane                       address@hidden
> >      <mailto:address@hidden>
> >      Boulder, CO 80301                   http://www.nwra.com