I appreciate the feedback in response to my earlier portability questions.
To help with managing Cygwin registry modifications and preventing undesired modification of the host environment and registry by a portable Cygwin, I have created two packages with the intent towards enabling a portable Cygwin by leveraging the PortableApps.com platform. The first wraps the Cygwin setup executable, and the second wraps a portable console that has been specifically configured for use with a portable Cygwin. The Cygwin directory structure itself sits outside the main “PortableApps” directory, at the root of the portable location. Because Cygwin modifies the registry both during a setup/update process and when starting a Cygwin session / running certain commands (such as "cygcheck -s"), the two Cygwin PortableApps.com packages are configured to block the other from launching while the one is running (though due to how I hacked this PortableApps.com Launcher capability, the resulting warning dialog will read like you have been blocked from starting a second instance of the same program). For similar reasons, it is also advised to not run both local and portable installs at the same time, but there is nothing to prevent a local setup or session from being started. Of course, there are ways around the protections that do exist, but doing so risks breaking the host environment or registry via undesired changes (due to how the PortableApps.com platform saves and restores the host environment). Also, I'm sure there are some usage scenarios this doesn't fully cover, but hopefully this at least provides a starting point. More details and information are available on the project site for Cygwin Setup Portable. * https://github.com/mesheets/PAF-CygwinSetupPortable * https://github.com/mesheets/PAF-CygwinConsolePortable Thank you, Matthew
