On Sat, Mar 21, 2015 at 10:58 PM, jungle Boogie <[email protected]> wrote:
> I'm really hoping its a rare case where a file name is this long: > > SWIGTYPE_p_f_p_switch_core_session_p_switch_event_p_switch_caller_profile_p_p_switch_core_session_p_p_apr_pool_t_enum_switch_originate_flag_t__switch_call_cause_t.cs > Fossil is not the only tool which will have problems with such auto-generated names. i have seen generated Java class names so long that they literally cannot be used on encrypted filesystems because the encrypted names are larger than the unencrypted names, and too long for the filesystem driver. Some examples: https://bugs.launchpad.net/backintime/+bug/1359776 https://bugs.launchpad.net/ecryptfs/+bug/344878 http://stackoverflow.com/questions/8239227/is-there-a-workaround-for-the-filename-length-limit-in-encfs -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
