Skip to content
This repository has been archived by the owner on May 17, 2019. It is now read-only.

Self-publish can't replace packages #1

Closed
ohanhi opened this issue Mar 19, 2016 · 0 comments
Closed

Self-publish can't replace packages #1

ohanhi opened this issue Mar 19, 2016 · 0 comments

Comments

@ohanhi
Copy link

ohanhi commented Mar 19, 2016

It would be great if elm_self_publish.py could replace an existing package by the same name and version. This seems like the usual case when developing an Elm package: self-publish the package under development, make some changes, self-publish again.

Another thing is that with Elm Native UI we need to replace the official core with a modified one, so the workflow now is the following:

  1. elm-make the first time in the project, which creates an elm-package.json and elm-stuff with the official core
  2. Remove official core by hand
  3. Self-publish the modified core
  4. Self-publish elm-native-ui

We could at least get rid of step 2 with this change. :)

@eeue56 eeue56 closed this as completed in 369bbd2 Mar 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant