On Sat, 23 Jul 2011 18:09:07 -0700 (PDT), Gé Weijers wrote: > Hi, > > I have just committed a fix for issues with long path names when > Fossil generates a tar file. What first looked simple wasn't because > of backward compatibility requirements. You can find my work in > branch > 'ge-tarfix'. > > I have attempted to use the rules laid out on the latest POSIX.1 > standard to generate files that are backward compatible with older > versions of 'tar'. These rules are described in the 'pax' section of > IEEE Std 1003.1-2008. The subset of features I used have been in the > standards for over 10 years, and GNU and BSD tar support them fully. > > If you use very long or non-ASCII file names and your 'tar' program > is out-of-date you may see a directory 'PaxHeader' show up. It > contains the file information your program was not able to recognize. > > All feedback is welcome. I'd especially like to have feedback on any > issues on non-Unix platforms. > > > Thanks, > > Gé Yep, works for me. Thanks
if I use Fossil version 1.19 [ba15af450d] 2011-07-23 22:13:12 i get 0ab5a139f847c13 -70ab5a139f847c13 ex-70ab5a139f847c13 x-70ab5a139f847c13 139f847c13 a139f847c13 flex-70ab5a139f847c13 xflex-70ab5a139f847c13 5a139f847c13 ab5a139f847c13 lex-70ab5a139f847c13 70ab5a139f847c13 b5a139f847c13 mxflex-70ab5a139f847c13 if i use fossil version 1.19 [2ef37b3b2a] 2011-07-24 00:36:46 UTC I get mxflex-70ab5a139f847c13 -- Rene _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
