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

[Dr. Volker Zell]

>>>>> Igor Pechtchanski writes:

    > Yes, .logs, or LOGS, or even just /usr/src/$PACKAGE[*] -- it's up to you.
    > As for deleting...  What I normally do with source packages is run
    > "./PKG-VER.sh prep", and then move PKG-VER.sh, PKG-VER.tar and
    > PKG-VER.patch to PKG-VER/CYGWIN-PATCHES.  That helps me keep my /usr/src
    > reasonably clean.  But that's just me, and others may not want stuff
    > deleted without their permission.
    > 	Igor
    > [*] If you choose the "no subdirectory" approach, beware that the g-b-s
    > as it stands will overwrite the logs.  That's why I suggested that the
    > logs be created with lowercase names initially, but renamed to upper case
    > in .spkg before building the source package.

Ok, I try again. Now after unpacking of the source archive you have the original
logfiles compressed under /usr/src. This archive gets unpacked to
/usr/src/$PACKAGE/.buildlogs during prep(). configure/make/check/install()
still put their logfiles to /usr/src/$PACKAGE/.sinst so it's easy to
diff them against their counterparts under /usr/src/$PACKAGE/.buildlogs.


 2005-10-10  Dr. Volker Zell  <dr.volker.zell@oracle.com>

 	* templates/generic-build-script (log_pkg_name): New.
 	(configurelogfile): New.
 	(makelogfile): New.
 	(checklogfile): Name change.
 	(installlogfile): New.
        (buildlogdir): New.
        (conf): Add logging.
 	(build): Add logging.
 	(check): Add logging.
 	(install): Add logging.
 	(spkg): Compress logfiles.
        (mkdirs): Incorporate buildlogdir.
        (prep): Unpack build logfiles.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: generic-build-script.patch
Type: text/x-patch
Size: 1344 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-apps/attachments/20051010/1af3db3a/attachment.bin>
-------------- next part --------------


Ciao
  Volker