Re: Autobuild time-saving proposal
On Thu, Jun 12, 2003 at 05:36:41PM +0200, Grzegorz B. Prokopski wrote:
> > My idea would be to add this testing step to the buildd process.
> See what SableVM main package is doing during it's build.
> (./debian/testsablevm file in sablevm package sources)
> As the last part of build process it runs itself twice,
> once - just to see the -V (version) output then - to run
> HelloWorld program which mostly guarantiees that the JVM
> is capable of running programs on certain arch.
My mail did not generate a lot of reply but enough to convince me that
some complex packages do some testing at build time and it would good to
provide a common framework.
> All another story is that:
> - it uses LD_LIBRARY_PATH so if the resulting packages
> are for ex. missing a lib - they won't work anyway
> (that shouldn't happen though)
> - it doesn't *install* the resulting package which
> would prove it to be actually instalable
So do you agree with me that testing the generated package could be a
good idea?
A single file in debian/ would be enough to catch missing files, broken
post/pre-rm/inst scripts, unuseable executable, ...
and most importantly in my eyes would allow some basic regression
testing of the packaging.
> - it requires additional build-time dependencies for that
> test to be possible
That would be nicely handled by the debian/control Depends: field and
the optionnal Test-Depends: field.
Note that dput (and friends, or lintian and friends) could do the same
test (when a debian/test file is present) on the locally build
packages before uploading.
Thanks for your reply,
Christophe
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
L'experience, c'est une connerie par jour mais jamais la même.
Reply to: