[Nautilus-list] problems building from cvs

[Ryan Muldoon <rpmuldoon students wisc edu>]

I am having trouble with the autogen.sh script when I do a fresh
checkout of nautilus from cvs.  I have the suggested versions of
automake and autoconf, so I am not quite sure what is wrong.  Basically,
what happens is that configure.in gets deleted somewhere during the
execution of the script, so autoconf can't make a configure script.  As
a result, automake can't run, and I don't have any Makefiles.  Is there
a solution to this problem?  I'd imagine that it is something dumb and
common that I am just not noticing.  I'd really appreciate some help, as
doing this is kind of impeding my ability to test a patch I made.


Also - is there something like eazel-hacking for general consumption?
I'd like to be able to try and mess around with working on Nautilus more
often, especially as my semester is over in a few weeks.  But, I'd
prefer to keep testing/source builds seperate from my "stable"
RPM-installed version of things.  Thoughts on this would be great too.
Thanks in advance.

    --Ryan