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

Write an EIP to specify how tooling should do package installation. #78

Open
pipermerriam opened this issue Nov 17, 2017 · 5 comments
Open

Comments

@pipermerriam
Copy link
Member

I'm thinking it would be good to specify how tooling should handle specifying what packages to install.

$ populus install owned
$ populus install owned==1.3.2
$ populus install [email protected]
$ populus install ./local-path-to/owned.json
$ populus install bzz://Zqme19sn....
$ populus install ipfs://Qm....

Something simple that lays out the syntax for the different ways that a user could specify what package they want installed so that the maintainers of tools can both know all the various ways a user may want to install a package.

@VoR0220
Copy link
Collaborator

VoR0220 commented Nov 20, 2017

hm...I'm not sure I understand what this EIP is proposing. What exactly would we be standardizing? The syntax all around? If so, I think this might be a tad out of scope.

@pipermerriam
Copy link
Member Author

I'm not sure an EIP is the right thing for this either. I'm thinking it may fit better in an "Implementers Guide" section within the documentation that still needs to be written for EthPM ( #71 )

@VoR0220
Copy link
Collaborator

VoR0220 commented Nov 20, 2017

Ah. Got it. A hard suggestion.

@ryan-rowland
Copy link

What's the shortcoming here in adopting the same patterns as npm?

@pipermerriam
Copy link
Member Author

@ryan-rowland I don't fully understand your question. Can you expand on what you mean?

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

3 participants