Date: Fri, 26 Feb 2010 01:47:11 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: FreeBSD-Hackers <freebsd-hackers@freebsd.org> Subject: Re: mktemp(1) in /tmp or $PWD? Message-ID: <7d6fde3d1002260147h428dc97ere1722e8b658d321e@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1002252225410.50330@qbhto.arg> References: <7d6fde3d1002251850m3d32904emece0182e905b84c5@mail.gmail.com> <7d6fde3d1002252100oc64434ci5f6783ff10a9f0ea@mail.gmail.com> <alpine.BSF.2.00.1002252225410.50330@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 25, 2010 at 10:27 PM, Doug Barton <dougb@freebsd.org> wrote:
> On Thu, 25 Feb 2010, Garrett Cooper wrote:
>
>> So what I did was I wrote up a patch to be *I know... here it comes*
>> more like GNU coreutils' copy of mktemp.
>
> What's the motivation for this?
Less typing and quirks because every other command line and
programmatic implementation I've run across (Linux, perl, python) uses
a similar paradigm with these sets of APIs. Example:
gcooper@orangebox ~/Downloads/susv4/susv4 $ uname -or
2.6.31-gentoo-r6 GNU/Linux
gcooper@orangebox ~/Downloads/susv4/susv4 $ mktemp
/tmp/tmp.5pmHxn3UfQ
gcooper@orangebox ~/Downloads/susv4/susv4 $ mktemp -d
/tmp/tmp.Q0PZbsf9BG
Compared with:
[gcooper@optimus ~]$ mktemp
usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
mktemp [-d] [-q] [-u] -t prefix
[gcooper@optimus ~]$ mktemp -d
usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
mktemp [-d] [-q] [-u] -t prefix
[gcooper@optimus ~]$ mktemp -d tmp.XXXXXXXXXX
tmp.cvZo2ABNRv
[gcooper@optimus ~]$ mktemp tmp.XXXXXXXXXX
tmp.KFnF5zomVn
> I'm a little confused about why we'd want to change this when the -t option already exists.
Because 1) -t requires that you spell out the entire path in a more
terse way, 2) tacks on more information in a more counter intuitive
manner, and 3) can only be used once per mktemp(3) call. Example:
[gcooper@optimus ~]$ mktemp -t tmp
/tmp/tmp.vAi6eCpD
[gcooper@optimus ~]$ mktemp -t tmp -d
/tmp/tmp.0f3Z9L5R
[gcooper@optimus ~]$ mktemp -t tmp -t notsotmp -d
/tmp/notsotmp.MTYHIGFs
[gcooper@optimus ~]$ mktemp -t foo.XXXXXX
/tmp/foo.XXXXXX.rGssqAZk
[gcooper@optimus ~]$ mktemp -t /something/foo.XXXXXX
mktemp: mkstemp failed on /tmp//something/foo.XXXXXX.J3CGs9dK: No such
file or directory
> Also, does POSIX say anything about what the default should be?
Nope. No mention of mktemp(1) in either v3 or v4 of the POSIX 1003.1 specs.
FWIW, the major advantages that BSD has on the coreutil's mktemp is
that it's half the size of coreutil's mktemp; plus, you only need to
call mktemp(1) once for multiple files. I have no intent on changing
that behavior because I think it's cool and more innovative than the
dumbed down single invocation mktemp(1) setup with coreutil's mktemp.
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d1002260147h428dc97ere1722e8b658d321e>