howdee,
im attempting to sort out all the warnings that
we see during the compile/link stages. i suspect
that some of them might be causing the PATH
issues in the runtime/batch-file.
im enclosing a patch that should not hurt anything
but allows me to write a short test script like:
#!/bin/sh
# test-install.sh
. functions
logerr . install.sh
and look thru the output later. i guess it is not
critical, like the earlier profile.d patch was not either.
however, i think that we might find a use for it.
sincerely, h
Index: functions
===================================================================
--- functions (revision 15247)
+++ functions (working copy)
@@ -1,5 +1,16 @@
+LOG_FN=$0.log
+ERR_FN=$0.err.log
+ALL_FN=$0.all.log
+function log1() { "$@" > "$LOG_FN"; }
+function log2() { "$@" 1>> "$LOG_FN"; }
+function log3() { "$@" &> "$ALL_FN"; }
+function log4() { "$@" 1> "$LOG_FN" 2> "$ERR_FN"; }
+function log5() { "$@" 1>> "$LOG_FN" 2>> "$ERR_FN"; }
+function log() { log1 date; log2 "$@"; log2 date;}
+function logerr() { log4 date; log5 "$@"; log5 date;}
+function nolog() { "$@" &> /dev/null; }
+function quiet() { nolog "$@"; }
function add_step() { steps=("[EMAIL PROTECTED]" "$@"); }
-function quiet() { "$@" &>/dev/null; }
# c:/dir/sub
function win_fs_path() { echo "$*" | sed 's,\\,/,g'; }
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
