Re: compiling from cvs
Brendon <bren@europe.nl.com> writes:
B> Lately i've been compiling more and more things from cvs to get the
B> most up to date versions, but not being familar with the compiling
B> process i sometimes have no clue what to do.
This is probably a bad idea, then. Developers tend to use CVS as a
place to store the absolutely-most-recent working copy of their code,
along with every version before it. This means that there's no
guarantee that the code in CVS works properly, much less even
compiles. It might be a good idea to use the CVS version of a program
if you're at least passively involved in its development and are
prepared to submit patches against the broken code; this implies
understanding how to build and test things already.
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.
--
David Maze dmaze@debian.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
Reply to: