Re: inadequate/inconsisten 'help pkg' message; problems with downloading

[Sergei Steshenko]

--- On Wed, 8/3/11, Sergei Steshenko <address@hidden> wrote:

> From: Sergei Steshenko <address@hidden>
> Subject: Re: inadequate/inconsisten 'help pkg' message; problems with 
> downloading
> To: address@hidden
> Date: Wednesday, August 3, 2011, 2:04 AM
> I have installed most of forge
> packages using command lines like this:
> 
> export
> TMP=/mnt/sdb8/sergei/AFSWD_debug/build/octave_forge_bundle
> && \cd
> /mnt/sdb8/sergei/AFSWD_debug/build/octave_forge_bundle
> &&
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/binsh/octave
> -V --no-init-file --eval 'pkg install -global -verbose -auto
> audio-1.1.4.tar.gz' 1>audio-1.1.4.tar.gz.install.log
> 2>&1
> .
> 
> After that starting 'octave' I see a number of warnings -
> please see the
> screen session below.
> 
> Do the
> 
> "
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../utl:
> No such file or directory
> "
> 
> indicate a real problem ? Are packages producing such
> messages supposed to
> work or they are DOA ?
> 
> During ocs-0.1.1 installation I see this:
> 
> copyfile
> /tmp/oct-OPe2qO/ocs-0.1.1/src/Mshichmanhodgesmosfet.oct
> /tmp/oct-OPe2qO/ocs-0.1.1/inst/i686-pc-linux-gnu-api-v45+
> 
> - from 'copyfile.m' I understand that
> 
> '/tmp/oct-OPe2qO/ocs-0.1.1/inst/i686-pc-linux-gnu-api-v45+'
> 
> is the destination directory. Is this the correct directory
> ?
> 
> Shouldn't it be in this case
> 
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+
> 
> which appears in the warning above ?
> 
> Thanks,
>   Sergei.
> 
> 
> Screen session BEGIN
> 
> GNU Octave, version 3.4.2
> Copyright (C) 2011 John W. Eaton and others.
> This is free software; see the source code for copying
> conditions.
> There is ABSOLUTELY NO WARRANTY; not even for
> MERCHANTABILITY or
> FITNESS FOR A PARTICULAR PURPOSE.  For details, type
> `warranty'.
> 
> Octave was configured for "i686-pc-linux-gnu".
> 
> Additional information about Octave is available at http://www.octave.org.
> 
> Please contribute if you find this software useful.
> For more information, visit http://www.octave.org/help-wanted.html
> 
> Read http://www.octave.org/bugs.html to learn
> how to submit bug reports.
> 
> For information about changes from previous versions, type
> `news'.
> 
> warning: function
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/share/octave/packages/statistics-1.0.10/fstat.m
> shadows a core library function
> warning: function
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/share/octave/packages/statistics-1.0.10/prctile.m
> shadows a core library function
> warning: dispatch is obsolete and will be removed from a
> future version of Octave; please use classes instead
> warning:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/share/octave/packages/integration-1.0.7/PKG_ADD:
> possible Matlab-style short-circuit operator at line 9,
> column 32
> warning: function
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/linear-algebra-2.0.0/i686-pc-linux-gnu-api-v45+/mgorth.oct
> shadows a core library function
> warning: function
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/share/octave/packages/multicore-0.2.15/gethostname.m
> shadows a built-in function
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../utl:
> No such file or directory
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../asm:
> No such file or directory
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../tst:
> No such file or directory
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../nls:
> No such file or directory
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../prs:
> No such file or directory
> warning: addpath:
> /mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../sbn:
> No such file or directory

[snip]

I've looked further into the issue of ocs-0.1.1 warnings. The package has
coming with it PKG_ADD file:

cat -n ocs-0.1.1/PKG_ADD
     1  dirlist = {"utl","asm","tst","nls","prs","sbn"};
     2  dir     = fileparts (mfilename ("fullpath"));
     3
     4  if (! exist (fullfile (dir, "inst"), "dir"))
     5    ## Run this if the package is installed
     6    for ii=1:length(dirlist)
     7      addpath (fullfile(dir,"..",dirlist{ii}),"-end")
     8    endfor
     9  else
    10    ## Run this if we are testing the package is installed without 
installation
    11    for ii=1:length(dirlist)
    12      addpath (fullfile(dir,"inst",dirlist{ii}))
    13    endfor
    14  endif
    15
    16  clear dirlist dir
.

If I understand correctly, due existence of its file directories listed in

     1  dirlist = {"utl","asm","tst","nls","prs","sbn"};

are added to path at

     7      addpath (fullfile(dir,"..",dirlist{ii}),"-end")
or
    12      addpath (fullfile(dir,"inst",dirlist{ii}))
.

But 'addpath' complains about non-existent directories, e.g.:

warning: addpath: 
/mnt/sdb8/sergei/AFSWD_debug/20110601/octave-3.4.2/lib/octave/packages/ocs-0.1.1/i686-pc-linux-gnu-api-v45+/../utl:
 No such file or directory
.

So, who's duty is it to create the missing paths which PKG_ADD wants to
add ?

Is it the duty of 'pkg.m' ?

Or maybe build mechanism of ocs-0.1.1 should have created them first ?

Or build mechanism of ocs-0.1.1 does create them, but 'pkg.m'  does not
copy them to destination ?

Thanks,
  Sergei.