When packaging Octave Forge packages for Fink, I have been removing functions that shadow identically-named functions in Octave core, since normally the situation has been that the package is older than the particular Octave release (e.g. 3.4.3 or 3.6.0), and I assumed that these functions had been subsumed into Octave core in identical form.
Would it be preferable for me _not_ to do this, however? Or maybe only do it when the m-file or oct-file in a package is _identical_ to what is in Octave core? I'll admit that I didn't do exhaustive testing of whether what I was removing was indeed identical to what was in core. Alex ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
