-
Simon Tatham authored
It was intended to ensure that people still working with DOS filename restrictions (or things approximating that, e.g. VFAT) wouldn't have trouble. Those days are surely long gone, and now zip -k is causing its own trouble with the new VS2010/VS2012 project files, which include pairs of filenames that become the same under the zip -k transformation and hence break the source archive build. [originally from svn r10155]
Simon Tatham authoredIt was intended to ensure that people still working with DOS filename restrictions (or things approximating that, e.g. VFAT) wouldn't have trouble. Those days are surely long gone, and now zip -k is causing its own trouble with the new VS2010/VS2012 project files, which include pairs of filenames that become the same under the zip -k transformation and hence break the source archive build. [originally from svn r10155]