Hi,
I'm talking about NAME_MAX which limits the length of basename of the
path and not MAX_PATH_LEN (or variant) which limits the length of WHOLE
path name.
I think it is possible to warn if user try to add (or retrieve from
repository) if the basename length exceeeds NAME_MAX-9.
# strlen(".svn-base") == 9
Actually, as you said, this number varies system by system but at very
least it is possible to avoid inconsistency of meta data file and the
file itself. In my case, there is a file but svn couldn't create meta
data file ("some_file_name.svn-base"). This cause lot of problems.
thanks!
shigeya
Erik Huelsmann wrote:
> On 10/22/07, Shigeya Suzuki <shigeya@wide.ad.jp> wrote:
>> Hi,
>>
>> I'm currently in little bit nasty situation.
>>
>> I accidentally committed a file with a filename length at 251 byte.
>> (Japanese Kanji Characters using UTF-8, 'LC_ALL="ja_JP.UTF-8"')
>>
>> I could commit, but I can't update, because filename length exceeds
>> 255-9 bytes, so svn could not write file with ".svn-base' appended.
>>
>> I believe svn should warn if user try to commit a file with more than
>> NAME_MAX-9 bytes of name.
>
> Which NAME_MAX do you suggest we use? The one from Windows, which is
> 65535? The one which also subtracts the length of your local path? (ie
> /home/some-very-long-user-name/sources-from-subversion/svn/trunk/...)?
>
> I'm sorry, but I don't see how Subversion can reliably make such a
> warning portable.
>
> bye,
>
>
> Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 22 11:42:15 2007