Skip to content
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 export: releases reexport #41

Open
tsafin opened this issue Jan 29, 2017 · 3 comments
Open

Package export: releases reexport #41

tsafin opened this issue Jan 29, 2017 · 3 comments

Comments

@tsafin
Copy link
Contributor

tsafin commented Jan 29, 2017

Projects which does have release package, should be handled specially (and might be handled even without any local recompilation).

i.e. for the intersystems-ru/webterminal there is latest release v3.2.2 which has special asset CacheWebTerminal-v3.2.2.xml:

  1. we propagate package metadata with GitHub repo metadata;
  2. set version to 3.2.2;
  3. copy CacheWebTerminal-v3.2.2.xml asset as the single container to install via package.json (.path attribute);
  4. Handle/propagate readme;
  5. And export this package as-is, without any recompilation
@tsafin tsafin added this to the Useful version 0.2 milestone Jan 29, 2017
@tsafin
Copy link
Contributor Author

tsafin commented Jan 29, 2017

I've done this way manually, for the initial propagation of an npm registry.

@nikitaeverywhere
Copy link

nikitaeverywhere commented Jan 29, 2017

@tsafin, could you please refer me to the guide of how to install, use & test your package manager?

@tsafin
Copy link
Contributor Author

tsafin commented Jan 29, 2017

@ZitRos wait a bit for 2nd article published. There will be some background, and some advices

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants