Re: Cygwin symlinks

> Sounds good. The non-Windows 0install command doesn't have any
> commands for creating archives, but leaves that to separate tools. It
> might even be worth contributing your patches to the Windows tar port.
> That seems more logical than putting a tar-creator in 0install itself.

There are two issues with using external tools for creating the archives on
Windows:

 Timestamps need to be stored in UTC for 0install, while almost all ZIP
tools use the local timezone instead. This may be configurable for some
archivers but the user has to know about this.

Our special-case handling of executable flags in the .xbit file definitely
does not get handled by any external archiver.

So I was thinking it would be a good idea to have a command that creates an
archive from a directory that will can be extracted exactly the same way it
was by 0install. Perhaps this should be a feature of the .NET version of
0publish rather than 0install itself?


------------------------------------------------------------------------------