> I appreciate all the work and testing that you're doing, but can I ask
> that you be more careful about the order and completeness of the files
> you commit to CVS? The whole automake situation was discussed at length
> many months ago, and it was decided then that because not everyone has
> an up-to-date version of automake installed, the compilation of ht://Dig
> should not be dependent on automake - that means you shouldn't commit
> changes to a Makefile.am without committing the corresponding changes
> to Makefile.in. Also, you should not remove any source files from the
> CVS tree until you've purged all dependencies from the tree. Similarly,
> you shouldn't add any new dependencies to the tree until you've added
> the files which are depended upon.
I think all these issue will be solved by simply making sure that 'make
distcheck' runs ok. Since it recompiles everything from fresh, in a separate
source tree and then run tests, it achieves all these checks at once.
> I'm trying to build RPMs from a clean snapshot of the CVS tree, and every
> time I run into a new error like this, I have to start over from scratch.
> It's a tedious process if I can't count on a cleanly buildable source
> tree, because each time I have to put together a patch to fix the error
> and rebuild the RPM. It may not sound like the best way to do things,
> but I'm kind of committed to working on the RPMs, and I'd rather have
> RPMs for testing purposes because they're more easily installed and
> removed from the test systems. If I can get a clean build, it'll be a
> lot easier to test small, incremental changes to a few programs without
> starting over from scratch each time.
I'm sure Marcel understands all this very well. Since he's in charge of
the standalone distribution of htword/htlib/htdb/db, he has to go thru all
this himself :-)
Cheers,
--
Loic Dachary
24 av Secretan
75019 Paris
Tel: 33 1 42 45 09 16
e-mail: [EMAIL PROTECTED]
URL: http://www.senga.org/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
