From: Enrico Scholz (enrico.scholz_at_informatik.tu-chemnitz.de)
Date: Wed 18 May 2005 - 23:08:34 BST
herbert_at_13thfloor.at (Herbert Poetzl) writes:
>> > while we are at it, how would I 'build' a release tar archive
>> > (i.e. clean everything up which doesn't go into your releases)
>> > or a source rpm from the cvs sources?
>> Do you mean something like 'make dist'?
>> rpms can be built with the usual 'rpmbuild -ta <tarball>.bz2'
> where does the tarball come from (using cvs)?
It comes from the 'make dist' mentioned above:
1. cvs co ## --> the files
2. autoreconf -i -f ## --> configure, Makefile.in's and other stuff
3. ./configure ... ## --> see below also;
## Makefile, config.status, util-vserver.spec
4. make dist ## --> util-vserver.spec, ChangeLog, the tarball
To set reasonable paths and options, you can try './build-all dist'
instead of 3. but this script is for my purposes only and documented
only by its source.
>> Dunno; next release will incorporate 'vwait' integration for
>> 'vserver ... stop' which needs some testing.
> well, _now_ is the right time to _get_ some testing. of course,
> without anything to test, there will be no testing ... ;)
That's the kind of tests which can only be done by the developer ;) But
other work and fear of zombies stopped me to play with 'vserver ... stop'
Vserver mailing list