<DIV>> GRASS bugtracker:</DIV>
<DIV>> this bug's URL: <A href="http://intevation.de/rt/webrt?serial_num=2877">http://intevation.de/rt/webrt?serial_num=2877</A></DIV>
<DIV> </DIV>
<DIV>> Debian Bug #287651:<BR>> <A href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287651">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287651</A></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Temporary files in GRASS C modules should use G_tempfile() or G__tempfile(), and GRASS scripts should be using the g.tempfile module:</DIV>
<DIV> </DIV>
<DIV>GRASS 5.7.cvs:~ > g.tempfile --help</DIV>
<DIV>Description:<BR> Creates a temporary file and prints the file name.</DIV>
<DIV>Usage:<BR> g.tempfile pid=value</DIV>
<DIV>Parameters:<BR> pid Process id to use when naming the tempfile<BR></DIV>
<DIV>Which writes into $MAPSET/.tmp/ ....</DIV>
<DIV> </DIV>
<DIV>Most of the GRASS scripts that have been rewritten for 5.7 use g.tempfile already.</DIV>
<DIV>Remaining to do:</DIV>
<DIV> </DIV>
<DIV>grass57-cvs$ grep -r '/tmp/' scripts/* | cut -f1 -d: | uniq<BR>scripts/i.oif/i.oif<BR>scripts/i.oif/i.oifcalc<BR>scripts/i.spectral/i.spectral<BR>scripts/r.plane/r.plane<BR>scripts/r.regression.line/r.regression.line<BR>scripts/r.univar.sh/r.univar.sh<BR></DIV>
<DIV>So not an unmanageable task.</DIV>
<DIV> </DIV>
<DIV>Please audit:</DIV>
<DIV>general/g.tempfile/main.c</DIV>
<DIV> <A href="http://freegis.org/cgi-bin/viewcvs.cgi/grass51/general/g.tempfile/main.c">http://freegis.org/cgi-bin/viewcvs.cgi/grass51/general/g.tempfile/main.c</A></DIV>
<DIV> </DIV>
<DIV>lib/gis/tempfile.c</DIV>
<DIV> <A href="http://freegis.org/cgi-bin/viewcvs.cgi/grass51/lib/gis/tempfile.c">http://freegis.org/cgi-bin/viewcvs.cgi/grass51/lib/gis/tempfile.c</A></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV>The 5.0 line is pretty much EOL'd at this point. Any patching is up to the Debian packagers to do. Rather than spending time fixing all, I'd suggest checking which modules are actually built, a large percentage are not.</DIV>
<DIV> </DIV>
<DIV>These should probably be fixed in the 5.4 CVS (subject to volunteer &/or external 5.0.x patching + merge [5.0->5.4 should be mostly drop in]).</DIV>
<DIV> </DIV>
<DIV>If no one else gets to it first I can work on updating the remaining 5.7 scripts after I get back to work sometime after the new year (*Also I think there are still some if [ $opt = (null) ] tests which still need to be changed to if [ -z "$opt" ]).</DIV>
<DIV> </DIV>
<DIV>It will be up to the debian packagers to decide if they want to back port these changes to 5.7.0 or wait for the 6.0beta series [6.0->5.7.0 should be mostly drop in].</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>A culled more general search of the 5.7 code turns up these as well:</DIV>
<DIV>imagery/i.ask/popup.c<BR>lib/db/stubs/BUILD.PROTO<BR>lib/db/dbmi_driver/mk_dbstubs_h.sh<BR>lib/gis/unix_socks.c<BR>lib/gis/gislib.dox<BR>lib/gis/win32_pipes.c<BR>lib/init/init.sh<BR>lib/init/make_location_epsg_g57.sh<BR>raster/r.digit/main.c<BR>raster/r.median/main.c<BR>raster/r.terraflow/description.html<BR>raster/r.terraflow/main.cc<BR>vector/v.out.ogr/description.html<BR></DIV>
<DIV> </DIV>
<DIV>from the top o' the year,</DIV>
<DIV>Hamish</DIV>
<DIV> </DIV></DIV><p>
<hr size=1>Do you Yahoo!?<br>
Yahoo! Mail - Find what you need with new enhanced search. <a href="http://us.rd.yahoo.com/evt=29917/*http://info.mail.yahoo.com/mail_250">Learn more.</a>