Rob Walker <[EMAIL PROTECTED]> writes:
> How long does it take g-wrap to be built?
Actually, it's not really how long it takes to build. It's more how
long it takes it to run a
make -q -C g-wrap || rm -rf g-wrap-install
test -e g-wrap-install || make -C g-wrap
test -e g-wrap-install || make -C g-wrap install
i.e. see if anything needs rebuilding, and if so, rebuild and
re-install.
It doesn't take that long, but it annoys some people when they're
rebuilding a lot and never touching g-wrap. The only reason we'd even
*consdier* special-casing g-wrap is that it really is a separate
package, and in the long run, may very well not come with gnucash...
However, I could easily be convinced that we should just always make
sure g-wrap is up to date, and if it's taking too long because it's
"overchecking" in it's make process, then spend a little time fixing
that.
> I like this one better, it saves developers from doing tech support.
> Q: "Why is my something doing something I don't understand?"
> A: "Make clean, and retest, then come back to us."
OK, so we have two different opinions now. Any tiebreakers :>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
