I don't think this rises to the level of being an installed script either. Somehow ...
16 years, 1 month ago (2009-09-22 04:30:16 UTC) #2
I don't think this rises to the level of being an installed script either. Somehow it has always worked to do things like tmp=$TMPDIR/scriptname.$pid.$USER and if that weren't enough there is always tmp=`{mktemp /tmp/scriptname.XXXXXX} I think it's great to have a bunch of good scripts that work for you, but the bar for putting them in plan9port has to be that they work well and are useful to a large enough fraction of the users to make everything know about them. Otherwise $PLAN9/bin will fill up with so many things that they won't all fit in one person's head, and that's a large part of the draw of the system. The drawback to that approach is that everything can't go in. I appreciate your suggestions and contributions and I hope you stick with Plan 9 and plan9port even though I've said no to these scripts.
On 2009/09/22 04:30:16, rsc wrote: > tmp=`{mktemp /tmp/scriptname.XXXXXX} Is a mktemp executable part of plan9port? ...
16 years, 1 month ago (2009-09-22 13:54:20 UTC) #3
On 2009/09/22 04:30:16, rsc wrote: > tmp=`{mktemp /tmp/scriptname.XXXXXX} Is a mktemp executable part of plan9port? I can't seem to find any mktemp files other than as part of libc. $ find . -name *mktemp* ./9pm/src/libc/port/mktemp.c
Issue 121043: cptmp - create a temporary file Created 16 years, 1 month ago by jdc Modified 16 years, 1 month ago Reviewers: rsc_swtch Base URL: Comments: 0