I don't see why a Readme.DEBIAN file in each package would be
difficult to manage. If needed, it could be generic, with the
same text in each package, such as:
By default installed packages are not available from the Octave
prompt. The functions from this package can be added to the Octave
path by typing
pkg load <package name>
at the Octave command line.
I note a discussion of autoloading packages here:
http://octave.1599824.n4.nabble.com/package-autoload-td4676287.html
particularly a comment by LachlanA;
> My personal belief is that the __unimplemented__ function, which
> currently tells us which package we should load, should just load
> the package and continue (unless the same function is implemented
> in multiple packages, in which case it should list all of those
> packages and give an error).
>
> That would most closely emulate the Matlab experience, while
> avoiding the problems Carnë described.
I would appreciate that. However, I'd be satisfied if the
__unimplemented__ function simply knew about all the functions available in
packages. (Currently it doesn't - the subject of another bug).
On Sat, Nov 24, 2018 at 5:43 AM Rafael Laboissière <raf...@debian.org>
wrote:
> [Moving this discussion from Bug#914373 into debian-octave.]
>
> * James Van Zandt <jim.vanza...@gmail.com> [2018-11-22 13:34]:
> >
> > [snip]
> >
> > Please provide a file /usr/share/doc/octave-statistics/README.Debian
> > with a note something like
> >
> > By default installed packages are not available from the Octave
> > prompt. The functions from this package can be added to the Octave
> > path by typing
> >
> > pkg load statistics
> >
> > at the Octave command line.
> >
> > [snip]
>
> The bug reporter also suggests to add README.Debian files for all
> other OF packages.
>
> Do the other members of the DOG agree with this change?
>
> Rafael
>
