-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package cygwin #26
Package cygwin #26
Conversation
Does this also help with Windows: Upgrading / downgrading 'esy' always reinstalls cygwin layer? |
Good question. This doesn't directly fix that issue, but it does mean that For CI to get these improvements - we'll need to make sure the npm cache is specified in the travis/appveyor cache sections. |
* Create build-cygwin.js * Update appveyor.yml / package.json * Update build step to remove cache * Continue fixing up files * Temporarily tweak package name * v0.0.100 * Update appveyor / build scripts * Revert package.json * Fix up comments * Remove unused yarn install * Try fixing appveyor * Add space * Add defaults folder Bump version -> 0.2.24 Set version to 0.2.1
This addresses #12 and #13 - we're taking a snapshot of Cygwin at build time, and including the
.cygwin
folder as part of our NPM package.The NPM package ends up being ~120MB, but low on dependencies - and installs much faster than the equivalent operation via the cygwin installer.
A few changes that were needed:
package.json
NODE_OPTIONS
to use a larger heap size, otherwise the publish step fails with an out-of-memory error./var/cache
folder, as cached packages are kept there, and we don't need those once they are unpacked - they'd just weigh the package down.