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

2005-10-17 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Pechtchanski on 10/16/2005 4:35 PM: Ah, thanks, I wasn't aware that setup.html recommended running spkg right after mkdirs. This will still create an (empty) ${log_pkg_name} tarball, which will get included in the source

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

2005-10-16 Thread Igor Pechtchanski
On Sat, 15 Oct 2005, Eric Blake wrote: According to Igor Pechtchanski on 10/14/2005 8:20 AM: One thing I didn't notice earlier about either this patch or your original one is that you removed the second cd $(topdir) from prep(). I know it looks superfluous, but it's there for a reason

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

2005-10-14 Thread Igor Pechtchanski
On Mon, 10 Oct 2005, Dr. Volker Zell wrote: 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() {

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

2005-10-14 Thread Igor Pechtchanski
On Fri, 14 Oct 2005, Igor Pechtchanski wrote: On Mon, 10 Oct 2005, Dr. Volker Zell wrote: 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

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

2005-10-10 Thread 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

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

2005-10-10 Thread Igor Pechtchanski
On Mon, 10 Oct 2005, Dr. Volker Zell wrote: 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

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

2005-10-10 Thread Dr. Volker Zell
Igor Pechtchanski writes: Sounds good, except can you please resubmit the diff with some context, preferably unified, just to make sure I can apply it cleanly? Uuups,my fault. So again: 2005-10-10 Dr. Volker Zell [EMAIL PROTECTED] * templates/generic-build-script

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

2005-10-10 Thread Igor Pechtchanski
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

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

2005-10-10 Thread Dr. Volker Zell
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