Re: CVS update: MODIFIED: . ...

Greg Stein <gstein@lyra.org> writes:
> Pull the version from configure.in -- that is the "original" source.
> svn_private_config.h is a couple steps down the configure/build process.

Yeah, I think you're right. It's not quite as easy to parse, but
still not a problem, and it *is* the master after all. That will
simplify some other things, too.

Thanks for the suggestion! Will do.

> Personally, I would recommend a short script that can pull the information
> from CVS, then add in the necessary bits. By putting it into the makefile, a
> person must first go through the full get-from-CVS, autogen, configure
> process.

You mean the script would do a checkout? Hmmm.

I had been avoiding that method, because what I want is to build a
dist from exactly what I have in my working copy. But maybe it's
always better to build from a known HEAD (especially after we have
atomic revisions, later).

Of course, that script would still live in the tree, so you'd still
have to have a working copy. But you wouldn't have to have a
configured working copy with a Makefile.

> Further, note that changes to the dist process would require changing
> Makefile.in, then re-running configure. A plain release script is much
> cleaner :-)

Yeah; have been rediscovering that very relevant fact lately. :-)

> I've attached an example script that I use for my "edna" application. I use
> a similar one for ViewCVS.

Thanks; will examine and perhaps rework the way dist-building works.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:35 2006