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

[pipermerriam]

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 owned==1.3.2@packages.pipermerriam.eth
$ 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]

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]

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]

Ah. Got it. A hard suggestion.

[ryan-rowland]

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

[pipermerriam]

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