[g-b-s Patch: next try] Write and save logfiles for configure/make/check/install

Dr. Volker Zell Dr.Volker.Zell@oracle.com
Mon Oct 10 19:49:00 GMT 2005


>>>>> Igor Pechtchanski writes:

    > On Mon, 10 Oct 2005, Dr. Volker Zell wrote:
    >> @@ -340,6 +349,7 @@
    >> cp $0.sig ${srcinstdir}/ ; \
    >> fi && \
    >> cd ${srcinstdir} && \
    >> +  tar cvjf ${log_pkg_name} *.LOG && rm *.LOG && \
    >> tar cvjf ${src_pkg} * )
    >> }
    >> finish() {

    > One small issue here: would it make sense to list the files explicitly for
    > both "tar" and "rm", instead of just using *.LOG?  Suppose the variable
    > values get changed?

    > This would, of course, require some rethinking of the variable values
    > (i.e., the explicit path), or we could just change it to

    > +  tar cvjf ${log_pkg_name} ${configurelogfile%%${srcinstdir}/} \
    > +       ${makelogfile%%${srcinstdir}/} ${checklogfile%%${srcinstdir}/} \
    > +       ${installlogfile%%${srcinstdir}/} && \
    > +    rm *.LOG ${configurelogfile%%${srcinstdir}/} \
    > +         ${makelogfile%%${srcinstdir}/} ${checklogfile%%${srcinstdir}/} \
    > +         ${installlogfile%%${srcinstdir}/} && \

    > (using bash-isms).

    > Comments?

No problem, but this time it's your turn :-) This takes way to long.
Please check in if nobody else objects.

    > 	Igor

Ciao
  Volker



More information about the Cygwin-apps mailing list