Skip to content
This repository has been archived by the owner on Jan 12, 2021. It is now read-only.

in case we have to upgrade the new version of require #7

Closed
jeonghanlee opened this issue Nov 28, 2017 · 1 comment
Closed

in case we have to upgrade the new version of require #7

jeonghanlee opened this issue Nov 28, 2017 · 1 comment
Assignees
Labels

Comments

@jeonghanlee
Copy link
Contributor

In case we have to upgrade the new version of require, what kind of actions should we have to do for entire E3 environment?

Do we have any automatic way to build the entire modules (existent in E3) with new require version?

If so, if one would like to use old require instead of new require, what can we do? How we can distinguish between them? Impossible to distinguish them?

Again, Chicken or the egg? we have to define the procedure properly not to happen this case in future.

@jeonghanlee jeonghanlee self-assigned this Nov 28, 2017
@jeonghanlee
Copy link
Contributor Author

BASE-REQUIRE-Others structure should be implemented. Complicated, but feasible .

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

No branches or pull requests

1 participant