So you want to write a package manager

Re:So you want to write a package manager by tadfisher on Sunday February 14, 2016 @12:49AM (#11097286)

For one, you can't install system-level dependencies with Maven. `gradle install <foo>` simply isn't a concept. Dependencies you download for a project are confined to that project, and optionally cached for other projects dependent on the same versioned artifacts.

The end result is that there is no "global" dependency like you would install with `npm install <foo>`. There is no dealing with dependency mismatches between projects that depend on "<foo> >= 1.2" for example, which can be a hassle to track down in the "global dependency installation" model most often used by these language-level package managers.

[ Parent | on HN ]

Re:So you want to write a package manager by meddlepal on Sunday February 14, 2016 @01:01AM (#11097317)

IMO this, the Maven and Gradle way is the way it should be. Global dependencies are a nightmare.

[ Parent | on HN ]

Re:So you want to write a package manager by klodolph on Sunday February 14, 2016 @04:54AM (#11097727)

What you're describing for Maven is exactly how NPM works. You run `npm install foo`, it installs foo locally, for the project you are working on. Again, I am having a hard time understanding what people think is different between Maven and NPM.

[ Parent | on HN ]