regression tests for pkg-jed packages

Rafael Laboissiere rafael at debian.org
Tue May 29 18:25:34 UTC 2007


* Jörg Sommer <joerg at alea.gnuu.de> [2007-05-29 18:45]:

> Of what checks do you think? I see the problem that you can't do so much
> checks, because the package isn't installed.

Are you talking about the tmexpand or the jed package?  I guess you are
referring to the later:

> What about forcing this for all packages? I suggest we add two targets
> check-arch and check-indep they run some tests after build, e.g. the last
> command of binary-arch must be -$(MAKE) debian/check-arch and for
> binary-indep respectively.

Typically, the upstream Makefile allows "make check" (this is recommended by
the GNU coding standards).  This should be called at the end of the build
rule of debian/rules.  BTW, this is what CDBS does.

Why are you suggesting to add the checks at the end of the binary-* rule?

> What do you think about rebuild as much as possible from scratch? I found
> out how John builds the configure script. Should we remove it and rebuild
> it?

Is it really necessary?  In Debian, we usually use the configure script
provided in the upstream tarball.  Only in rare cases it is necessary to
rebuild it with autoconf, in order to fix something broken.  If jed's
configure isn't broken, don't fix it.

-- 
Rafael



More information about the Pkg-jed-devel mailing list