Policy of refering to packages? Policy of choosing package for ML-compatible functions?

[Olaf Till]

Dear maintainers,

as mentioned in a recent post at the help list

http://lists.gnu.org/archive/html/help-octave/2016-12/msg00134.html

Octave may refer to the wrong OF package for functions not in core. It
seems that the reference only considers in which ML toolbox the
corresponding function is implemented.

I could just file a bug, but I think it would be better to discuss and
decide on a policy for these references. Problems could be that a
function may not yet be implemented even in OF and that a function may
be moved from one package to a different one.

This can't be separated from the question if a ML-compatible function
should always be contained in a package corresponding to the
respective ML-toolbox. So I think this issue should also be discussed
in this context. This had been attempted by Julien in

http://lists.gnu.org/archive/html/octave-maintainers/2015-08/msg00100.html

but there was no discussion.

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

signature.asc
Description: Digital signature