[Pkg-octave-devel] check.m for the forge packages

[John W. Eaton]

On 20-Mar-2008, Ólafur Jens Sigurðsson wrote:

| On Thu, Mar 20, 2008 at 04:35:22PM +0100, Rafael Laboissiere wrote:
| > * Ólafur Jens Sigurðsson <ojsbug at gmail.com> [2008-03-20 00:31]:
| > 
| > > The implementation in octave-pkg-dev sounds nice. But I am just not
| > > getting the point of all this. Is this really neccesery?
| > 
| > Nearly all packages maintained by the DOG run tests.  This is also typically
| > the case in Debian as general.  Running tests at package build is of great
| > help to detect problems before uploading or even on the autobuilders.
| 
| Yes, that's what I thought but looking at the source that does call
| the test routine there is no checking if the test succeeded, so this
| is just a visual for the user and has nothing to do with automation?
| 
| If that is the case, then I can do some other tests that are not based
| on the test function in octave for those packages that don't have that
| implemented.

I'm not sure I understand what you mean by this.  If you are planning
to test the Octave functions themselves, then please add the tests to
the source files you are testing by using the test/assert
functionality that is in Octave, and submit the changes to the
upstream maintainers.  That way, all users of Octave and its packages
benefit, not just people using Debian packages.

Thanks,

jwe