Jason van Zyl wrote:
>
> So update descriptors
> Generate
Once you have bootstrapped, you may find it easier/faster to generate using
"build gump scripts". Since the shell / command interpreter doesn't like
the scripts it is actually running being changed on it, I have a bin/build
that looks like this:
cd /data/gump
bash build.sh $*
test x$1 = xgump && (
cd /export/home/rubys/gump/work
test build.sh -nt /data/gump/build.sh && cp -p build.sh /data/gump
test ! -f /data/gump/build.sh && cp -p build.sh /data/gump
test update.sh -nt /data/gump/update.sh && cp -p update.sh /data/gump
test ! -f /data/gump/update.sh && cp -p update.sh /data/gump
)
> build
>
> can i bypass the cvs update?
Absolutely. What you are describing is pretty close to my normal cycle.
Every couple of days (or perhaps once a week, depending on how I feel) I do
a complete gump run on my development machine after first verifying that
the the projects I care about look pretty sane. Once done, I generally
only do build commands, with an occasional cvs update.
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
