Glenn Fowler wrote: > On Tue, 16 Jun 2009 20:24:39 +0200 Roland Mainz wrote: > > Casper.Dik at sun.com wrote: > > > >On Tue, Jun 16, 2009 at 09:55:30AM +0200, Casper.Dik at Sun.COM wrote: > > > >> > > > >> >/usr/bin already has an mktemp. How does it differ from the GNU > > > >> >version? Ah, there's an option conflict, sadly (-u is "--dry-run" in > > > >> >GNU, but "unsafe operation" in Solaris). > > > >> > > > >> Solaris' mktemp takes after the OpenBSD mktemp. > > > > > > > >What is the point of the Solaris mktemp(1) -u option though? Why would > > > >anyone choose "unsafe operation"? > > > > > > It came from OpenBSD. > > > > > > I can understand the reason, though, you can't always want to create a > > > file, you may want an unique value: > > > > > > unique=$(mktemp -u XXXXXX) > > > Ok... that makes sense... :-) > > > Erm... what is the stabilty state of "-u" - wasn't it "Commited > > Obsolete" ? If that's the case it may be nice to get rid of the > > "Obsolete" and poke the GNU coreutils maintainers to rename the "dryrun" > > option to something else (I'll poke AST+BSD upstream to do the same for > > their "mktemp" command (e.g. clarify documentation)). > > how would you clarify this: > > -u, --undo|unsafe|unwise > Remove the file/directory before exiting. Who would want > to do that. > > version mktemp (AT&T Research) 2009-05-01
See the other email with the patch I send a few seconds to you (ahhgllrr... I forgot to update the version number (new patch follows)). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;)
