You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 )
I'm thinking it would be good to specify how tooling should handle specifying what packages to install.
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.
The text was updated successfully, but these errors were encountered: