Currently etckeeper has two different mechanisms for creating temporary files. There's no clear reason for that, and it caught me out when I was trying to update some of the scripts for my own purposes.
I don't particularly mind how this is resolved, but I'd like it resolved in some consistent fashion! I've made two patches for two different resolutions:
- Allow either
mktemp
ortempfile
everywhere (best for backwards compatibility, as it'll keep working for folk who don't havemktemp
) - Consistently assume
mktemp
is available (best for simplicity)
Thanks, I've applied the first patch. It looks like all the code that assumed mktemp was available only ran when using darcs, so there are presumably systems where mktemp is not available that the second patch would break. done --?Joey