Hello,
some days ago i discovered a strange effect.
I wanted to execute a 'svn status -u' in a completely write protected
filesystem.
This produces an error-message which i didn't expect.
'svn: Can't open '.svn/tmp/tempfile.tmp': No such file or directory'
Why does the simple status query write to the filesystem?
After some gdb-session i figured out two functions which use temporary
files
and which try to place them into the current '.svn' directory.
1. svn_wc_translated_file()
2. svn_wc_create_tmp_file()
I changed the implementation to use 'svn_io_temp_dir()' and my problem
disappeared.
Now come the questions?
1. Why don't these (kind of) functions use svn_io_temp_dir() ?
2. Wouldn't it be wise to use for nearly any call to
'svn_io_open_unique_file'
a temp path delivered by svn_io_temp_dir() ? Because these files
don't have fix names and therefore have all a 'temporary' nature
3. Wouldn't it be more comfortable to integrate the call sequence
-svn_io_temp_dir()
-svn_path_join
-svn_io_open_unique_file
into one function named 'svn_io_open_unique_tmp_file' ?
thus
Confidentiality note:
The information in this email and any attachment may contain confidential and proprietary information of Heidelberger Druckmaschinen AG and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, we kindly ask you to notify the sender immediately and to delete this email and any attachment from your system.
Received on Thu Oct 12 17:09:57 2006