Re: compiling from cvs
David Z Maze <dmaze@debian.org> wrote:
>Brendon <bren@europe.nl.com> writes:
>B> i'm trying to compile konverse from cvs, how would i usually go about this
>B> when there's no configure script,
>
>Yup. Storing generated files (like configure) in CVS is generally a
>poor idea, since they can vary greatly between build machines and
>versions of unrelated software.
In the particular case of configure scripts, they don't vary between
build machines, but they do vary depending on your version of autoconf
(and possibly automake, if you have an aclocal.m4). Running something
like 'aclocal && autoheader && autoconf' often generates the required
files, provided again that you have autoconf and automake installed;
there may even be a script in the CVS repository called autogen.sh or
release.sh or similar which automates this.
Opinions on whether to store configure scripts in CVS vary (q.v.
debian-devel). Although storing them often means large diffs, it can
help make the release process more resilient if a number of developers
are involved. At least the autoconf project stores its configure script
in CVS, so it clearly doesn't cause fatal problems, although they may do
that for bootstrapping reasons more than anything else.
--
Colin Watson [cjw44@flatline.org.uk]
Reply to: