Eric Gillespie <epg@pretzelnet.org> writes:
> Do you honestly think the situation of importing */tmp itself* is
> something to worry about? Remember that importing directories
> *in* /tmp won't cause a problem if a tmpfile is stored in /tmp;
> they'd have to import /tmp itself.
Do I personally think it's a big concern? Not really. But if we can
have a solution that fixes all the possible problems, why avoid it?
Especially when the solution is in the direction of functionality that
some of us already desire (the import exclusions).
> All commands that can operate outside a wc store tmp files in the
> current directory: mkdir, cp, rm, etc. With import it is most
> noticeable because the file itself gets imported, but i say it is
> a problem even outside import. Out of all the programs i use,
> only one clutters my home directory with its tmp files: svn. We
> have specialized tmp directories for a reason.
Cluttering with tmpfiles? Okay, so my use of "fixes all the possible
problems" doesn't include your concern that tmpfiles are left
(apparently at some ridiculous rate, either because you constantly
fail to commit successfully, or because there are other problems in
Subversion) in your home directory. I can accept that as a legitimate
itch.
We've long agreed that APR temp directory support is Good Thing --
there's no question there. But as an aside, I'm dying to know what
Subversion, or you, is doing so wrong that your home directory is
"cluttered" with tmpfiles. I never have more than one
Subversion-related tmpfile outside of a .svn directory at a time. Is
anyone else experiencing this problematic cluttering?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 13 04:25:10 2002