Greg Stein <gstein@lyra.org> writes:
> I'm getting tired of people suggesting running autogen.sh :-) This is the
> second or third, and Ben keeps saying it, too...
Don't get so tired, Greg. :-)
Sure, one can often do "./gen-make.py build.conf" instead of
re-running autogen.sh. In any system with a hierarchy of operations,
there will always be commands that are supersets of other commands
(e.g., "Have you tried rebooting?").
If one can keep it all straight in one's head, so much the better.
But if not, it's easy enough just to give simple advice that one knows
will work every time.
Note that I'm not protesting your posting of the more efficient
recipe, which is welcome and useful. But there's simply no need to
chide those who post suggesting the less-efficient superset. They're
right, too, and their posts are equally useful, even if they lean the
other way in the convenience-vs-efficiency tradeoff.
-K
> If files are added, deleted, moved, then running autogen.sh is overkill.
> Just do the following:
>
> [gstein@suntzu svn]$ ./gen-make.py build.conf
> [gstein@suntzu svn]$
>
> That is it.
>
> autogen.sh does the above, plus other stuff which is totally unnecessary
> when dealing with file changes. And definitely: you do *not* need to run
> configure or anything like that. Just run gen-make and then "make".
>
> Cheers,
> -g
>
> --
> Greg Stein, http://www.lyra.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
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:47 2006