I was using the `react-native` package which I installed globally with `npm`. Now it says at the first line after executing the `init` command. The following:

    Installing react-native from npm...
    Consider installing yarn to make this faster: https://yarnpkg.com

So I was checking that website and it looked interesting to me, but I don&#39;t exactly know what it would be. At first, I thought that I would need `brew` to install `yarn`, so I could yarn to install `npm`. But now I think that `yarn` is a replacement of `npm`. Is that a correct statement?

Why would I like to have so many package managers?

I understand that it&#39;s useful for software like [Atom][1] or [Visual Studio Code][2] to have their own package manager. But for development, I do not see the reason why someone would like to use four different package managers (brew for &#39;primary software&#39;, `yarn` for `npm` packages, npm for backend modules and bower for front-end libraries). How can  this package manager forest be untangled?

  [1]: https://en.wikipedia.org/wiki/Atom_(text_editor)
  [2]: https://en.wikipedia.org/wiki/Visual_Studio_Code



What is the difference between brew, yarn, and npm?

Is it possible to use RPM or YUM or any other package manager in Linux, specifically CentOS, to install a package either already downloaded or from repo to a custom location without admin/root access?

I tried building from sources, using cmake, configure, make, make install etc, but, it ended up having so many dependencies one after other.

Or are there any better alternatives?

How to install packages in Linux (CentOS) without root user with automatic dependency handling?

One of my biggest frustrations with my favorite language is the effort it takes to get different libraries working for together under one unified development environment.  My biggest wish is to just be able to tell my IDE, or whatever, that I need a certain library, and it takes care of downloading it, compiling it(if necessary), installing it, then setting up the include and library paths.

What I want is [this](http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c), but for C++.  I would prefer if it works with Visual Studio, but gcc is okay too.  Or if it is it&#39;s own separate system, that&#39;s fine too.  It does, however, have to work in Windows.

What promising projects are out there to solve this problem?

Are there any efforts to create a package manager for C++?

I&#39;m a bit miffed by the python package installation process. Specifically, what&#39;s the difference between packages installed in the dist-packages directory and the site-packages directory?

What&#39;s the difference between dist-packages and site-packages?

Why does, for example, a Grunt plugin define its dependency on grunt as &quot;**peer dependencies**&quot;?

Why can&#39;t the plugin just have Grunt as its own dependency in **grunt-plug/node_modules**?

Peer dependencies are described here: https://nodejs.org/en/blog/npm/peer-dependencies/

But I don&#39;t really get it.

***Example***

I&#39;m working with AppGyver Steroids at the moment which uses Grunt tasks to build my source files into a /dist/ folder to be served on a local device. I&#39;m quite new at npm and grunt so I want to fully comprehend what is going on.

So far I get this:

**[rootfolder]/package.json** tells npm it depends on the `grunt-steroids` npm package for development:

      &quot;devDependencies&quot;: {
        &quot;grunt-steroids&quot;: &quot;0.x&quot;
      },

Okay. Running npm install in **[rootfolder]** detects the dependency and installs grunt-steroids in **[rootfolder]/node_modules/grunt-steroids**.

Npm then reads **[rootfolder]/node_modules/grunt-steroids/package.json** so it can install `grunt-steroids` own dependencies.:

 

    &quot;devDependencies&quot;: {
        &quot;grunt-contrib-nodeunit&quot;: &quot;0.3.0&quot;,
        &quot;grunt&quot;: &quot;0.4.4&quot;
      },
    &quot;dependencies&quot;: {
        &quot;wrench&quot;: &quot;1.5.4&quot;,
        &quot;chalk&quot;: &quot;0.3.0&quot;,
        &quot;xml2js&quot;: &quot;0.4.1&quot;,
        &quot;lodash&quot;: &quot;2.4.1&quot;
      },
    &quot;peerDependencies&quot;: {
        &quot;grunt&quot;: &quot;0.4.4&quot;,
        &quot;grunt-contrib-copy&quot;: &quot;0.5.0&quot;,
        &quot;grunt-contrib-clean&quot;: &quot;0.5.0&quot;,
        &quot;grunt-contrib-concat&quot;: &quot;0.4.0&quot;,
        &quot;grunt-contrib-coffee&quot;: &quot;0.10.1&quot;,
        &quot;grunt-contrib-sass&quot;: &quot;0.7.3&quot;,
        &quot;grunt-extend-config&quot;: &quot;0.9.2&quot;
      },

The &quot;**dependencies**&quot; packages are installed into **[rootfolder]/node_modules/grunt-steroids/node_modules** which is logical for me. 

The &quot;**devDependencies**&quot; aren&#39;t installed, which I&#39;m sure is controlled by npm detecting I&#39;m just trying to use `grunt-steroids`, and not develop on it.

But then we have the &quot;**peerDependencies**&quot;.

These are installed in **[rootfolder]/node_modules**, and I don&#39;t understand why there and not in **[rootfolder]/node_modules/grunt-steroids/node_modules** so that conflicts with other grunt plugins (or whatever) are avoided?

Why use peer dependencies in npm for plugins?

I know `pip` is a package manager for python packages. However, I saw the installation on IPython&#39;s website use `conda` to install IPython.

Can I use `pip` to install IPython? Why should I use `conda` as another python package manager when I already have `pip`?

What is the difference between `pip` and `conda`?

What is the difference between pip and conda?

**How do I list the *user-installed / envirorment*  package ONLY in `npm`?** 

When I do `npm -g list` it outputs every package and their dependencies, instead I&#39;d like to see the packages installed in the **current working project or envirorment.**

How to list npm user-installed packages?

I was watching [this][1], and, as you can see, the first command I am told to put in is:

    sudo apt-get install python-setuptools

When I do this, it outputs:

    sudo: apt-get: command not found

I have no idea why this is the case.

How can I resolve this so I am following the tutorial correctly?

  [1]: https://www.youtube.com/watch?v=oT1A1KKf0SI







Why is the apt-get function not working in the terminal on Mac OS X v10.9 (Mavericks)?

I&#39;m able to update pip-managed packages, but how do I update pip itself? According to `pip --version`, I currently have pip 1.1 installed in my virtualenv and I want to update to the latest version. 

What&#39;s the command for that? Do I need to use distribute or is there a native pip or virtualenv command? I&#39;ve already tried `pip update` and `pip update pip` with no success.

How do I update/upgrade pip itself from inside my virtual environment?

Can I install/upgrade packages from GitHub using [conda][1]?

For example, with `pip` I can do:

    pip install git+git://github.com/scrappy/scrappy@master

to install `scrappy` directly from the `master` branch in GitHub. Can I do something equivalent with conda?

If this is not possible, would it make any sense to install pip with conda and manage such local installations with pip? 



  [1]: http://www.continuum.io/blog/conda

Conda: Installing / upgrading directly from github

Suppose I&#39;m writing a library A, that depends on another library, monolog for instance.

I want to install the latest version of monolog, so I just put this inside composer.json:

    {
        &quot;require&quot;: {
            &quot;monolog/monolog&quot;: &quot;*.*.*&quot;
        }
    }

Then I run `$ php composer.phar install`.

I was expecting to find the version installed, inside composer.lock, but it&#39;s not there:

	{
		&quot;hash&quot;: &quot;d7bcc4fe544b4ef7561918a8fc6ce009&quot;,
		&quot;packages&quot;: [
			{
				&quot;package&quot;: &quot;monolog/monolog&quot;,
				&quot;version&quot;: &quot;dev-master&quot;,
				&quot;source-reference&quot;: &quot;2eb0c0978d290a1c45346a1955188929cb4e5db7&quot;
			}
		],
		&quot;packages-dev&quot;: null,
		&quot;aliases&quot;: [

		],
		&quot;minimum-stability&quot;: &quot;dev&quot;,
		&quot;stability-flags&quot;: [

		]
	}

I need the version because I want to tie my library to a specific set of versions, eg: If I find the version is 1.3.5, in my composer.json I would like to put something like this:

        &quot;require&quot;: {
            &quot;monolog/monolog&quot;: &quot;1.3.*&quot;
        }

Any ideas?

composer: How to find the exact version of a package?

coming from a `Node` environment I used to install a specific version of a vendor lib into the project folder (`node_modules`) by telling `npm` to install that version of that lib from the `package.json` or even directly from the console, like so:

    $ npm install express@4.0.0

Then I used to import that version of that package in my project just with:

    var express = require(&#39;express&#39;);

Now, I want to do the same thing with `go`. How can I do that?
Is it possible to install a specific version of a package? If so, using a centralized `$GOPATH`, how can I import one version instead of another?

I would do something like this:

    $ go get github.com/wilk/uuid@0.0.1
    $ go get github.com/wilk/uuid@0.0.2

But then, how can I make a difference during the import?

How do I import a specific version of a package using go get?

I try to deploy my app and sometimes get this error: 

    Failure 
    [INSTALL_FAILED_CONTAINER_ERROR] 

I tried to google it but don&#39;t find what the error means or what it&#39;s 
caused by. I deploy via IDE (IntelliJ) the file gets copied to the 
device to the /data/local/tmp (unrooted Huawei Ideos, running 2.2), 
but the package manager doesn&#39;t seem to like it. Before installing the 
apk, I already removed the app from the device beforehand. I also made 
sure there was no old file under /data/local/tmp on the device. Still 
I&#39;m getting this error now. 
The package should be signed with the debug key, since I deploy via 
IDE by &#39;running&#39; the app. 

    $ pwd 
    /data/local/tmp 
    $ ls -l 
    -rw-rw-rw- shell    shell    17257686 2011-04-21 20:31 
    com.company.shop 
    $ pm install -r com.company.shop 
            pkg: com.company.shop 
    Failure [INSTALL_FAILED_CONTAINER_ERROR]

What does it mean and how to resolve it?

**Edit/Update:**

I can avoid the error when not allowing the app to be installed on sdcard, setting

    android:installLocation=&quot;internalOnly&quot;

in the manifest. It&#39;s ok for development, but for production, it&#39;s not really what I want - since my app is quite large with 17mb; therefore I prefer it to be on sdcard.
How to ever be able to install it on the external memory without rooting (since this is the only way I could delete /mnt/secure/asec/smdl2tmp1.asec, which seems to be one solution as well).

What does this mean: Failure [INSTALL_FAILED_CONTAINER_ERROR]?

I tried [this][1]:

    sudo npm cache clean -f
    sudo npm install -g n
    sudo n stable

...but it didn&#39;t work.

How do I do this on Windows?

  [1]: http://davidwalsh.name/upgrade-nodejs


How can I update npm on Windows?

I used [sdkman][1] to install groovy which went fine.  Where is the installed package now? I need the path for it.  I am on Ubuntu 14.04.

  [1]: http://sdkman.io/

Where does sdkman install packages?

I seem to have diverging versions of `rustc` and `cargo` (I think), 

&lt;!-- language: none --&gt;

    $ rustc -V
    rustc 1.9.0 (e4e8b6668 2016-05-18)
    $ cargo -V
    cargo 0.10.0-nightly (10ddd7d 2016-04-08)

Is there a command akin to 

&lt;!-- language: none --&gt;

    pip install --upgrade pip 

for upgrading `cargo`? I.e. something like

&lt;!-- language: none --&gt;

    cargo install --upgrade cargo

Is there a command to update Cargo to the latest official release?

I&#39;m new to npm and don&#39;t really understand what should go into dependencies vs. devDependencies. I know that for testing libraries they should go into dev, but how about for things like babel and webpack? Should they be in dev too, because they&#39;re only used to transcompile es6 and JSX into vanilla JS? My understanding is that when you deploy to heroku, it do the transcompiliation with the necessary libraries already, so there&#39;s no need to host them on production?

      &quot;dependencies&quot;: {
        &quot;babel-core&quot;: &quot;^6.7.7&quot;,
        &quot;babel-eslint&quot;: &quot;^6.0.4&quot;,
        &quot;babel-loader&quot;: &quot;^6.2.4&quot;,
        &quot;babel-plugin-react-transform&quot;: &quot;^2.0.2&quot;,
        &quot;babel-plugin-transform-object-rest-spread&quot;: &quot;^6.6.5&quot;,
        &quot;babel-plugin-transform-react-display-name&quot;: &quot;^6.5.0&quot;,
        &quot;babel-polyfill&quot;: &quot;^6.7.4&quot;,
        &quot;babel-preset-es2015&quot;: &quot;^6.6.0&quot;,
        &quot;babel-preset-react&quot;: &quot;^6.5.0&quot;,
        &quot;bootstrap&quot;: &quot;^3.3.7&quot;,
        &quot;css-loader&quot;: &quot;^0.23.1&quot;,
        &quot;es6-promise&quot;: &quot;^3.2.1&quot;,
        &quot;eslint&quot;: &quot;^2.9.0&quot;,
        &quot;eslint-plugin-babel&quot;: &quot;^3.2.0&quot;,
        &quot;eslint-plugin-react&quot;: &quot;^5.0.1&quot;,
        &quot;express&quot;: &quot;^4.13.4&quot;,
        &quot;extract-text-webpack-plugin&quot;: &quot;^1.0.1&quot;,
        &quot;file-loader&quot;: &quot;^0.9.0&quot;,
        &quot;lodash&quot;: &quot;^4.15.0&quot;,
        &quot;react&quot;: &quot;^15.0.2&quot;,
        &quot;react-addons-css-transition-group&quot;: &quot;^15.0.2&quot;,
        &quot;react-dom&quot;: &quot;^15.0.2&quot;,
        &quot;react-redux&quot;: &quot;^4.4.5&quot;,
        &quot;react-transform-catch-errors&quot;: &quot;^1.0.2&quot;,
        &quot;react-transform-hmr&quot;: &quot;^1.0.4&quot;,
        &quot;redbox-react&quot;: &quot;^1.2.3&quot;,
        &quot;redux&quot;: &quot;^3.5.2&quot;,
        &quot;redux-form&quot;: &quot;^6.1.0&quot;,
        &quot;rimraf&quot;: &quot;^2.5.2&quot;,
        &quot;style-loader&quot;: &quot;^0.13.1&quot;,
        &quot;webpack-dev-middleware&quot;: &quot;^1.6.1&quot;,
        &quot;webpack-hot-middleware&quot;: &quot;^2.10.0&quot;
      },
      &quot;devDependencies&quot;: {
        &quot;babel-register&quot;: &quot;^6.9.0&quot;,
        &quot;chai&quot;: &quot;^3.5.0&quot;,
        &quot;mocha&quot;: &quot;^2.5.3&quot;,
        &quot;sinon&quot;: &quot;^1.17.4&quot;,
        &quot;webpack&quot;: &quot;^1.13.2&quot;
      }

Do you put Babel and Webpack in devDependencies or Dependencies?

I&#39;m trying to understand this part: http://getcomposer.org/doc/02-libraries.md#lock-file

&gt; this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project&quot;

Does that mean that if project P depends on library A, and library A depends on library B v1.3, project P won&#39;t care about the version of library B, and will possibly install B 1.4 instead? What&#39;s the point then?

Or does it mean the opposite, as one would expect from a dependency manager?

composer.lock: how does it work?

Emacs 24 [looks like it will have][1] a package manager. What package management options are there for Vim?

  [1]: http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg00272.html

Package(Plugin) Management for Vim

Is there a [package manager][1] for Java like [easy_install][2] for Python ?  
I&#39;m looking for a solution usable from the command line and not from an IDE.


  [1]: http://en.wikipedia.org/wiki/Package_manager
  [2]: http://en.wikipedia.org/wiki/Easy_install

Is there a package manager for Java like easy_install for Python?

How is [Bower][1] different than [jspm][2]? Can Bower provide jspm functionality about [SystemJS universal module loader][3]?


  [1]: http://bower.io/
  [2]: http://jspm.io/
  [3]: https://github.com/systemjs/systemjs

Package Manager: Bower vs jspm

Although several thousand Emacs Lisp libraries exist, GNU Emacs, until version 24.1 did not have an (internal) package manager.

I guess that most users would agree that it is currently rather inconvenient to find, install and especially keep up-to-date Emacs Lisp libraries.

**Pages that make life a bit easier**

For versions of Emacs older than 24.1:

 - [Emacs Lisp List](http://www.damtp.cam.ac.uk/user/sje30/emacs/ell.html) - Problem: I see dead people (links).
 - [Emacswiki](http://www.emacswiki.org) - Problem: May contain traces of nuts (malicious code).
 - [Emacsmirror](http://github.com/emacsmirror/p/wiki) - The package repository I am working on. Problem: No package manager supports it natively yet.

**Some package managers**

It&#39;s not that nobody has tried yet. (Some of these did not exist when this question was asked.)

 - **[auto-install](http://www.emacswiki.org/emacs/AutoInstall)**
 - **[borg.el](https://github.com/emacscollective/borg)** - Assimilate Emacs packages using Git submodules.
 - **[el-get.el](http://www.emacswiki.org/emacs/el-get.el)** - Supports many sources.
 - [elinstall.el](http://repo.or.cz/w/elinstall.git)
 -  **[epackage](http://github.com/jaalto/project--emacs-epackage)** aka DELPS - Debian packaging concepts applied to Emacs Lisp packages.
 - [epkg.el](http://gitlab.com/tarsius/epkg) - This is now just a tool for browsing the Emacsmirror.
 - [install.el](http://www.iro.umontreal.ca/~monnier/elisp/install.el)
 - [install-elisp.el](http://www.emacswiki.org/emacs/install-elisp.el)
 - [jem-pkg.el](http://www.jemarch.net/jempkg.html)
 - **[package.el](http://tromey.com/elpa/)** - ELPA. Seems like it will be included in Emacs 24.

---

   ***UPDATE -- package.el is included in GNU Emacs, starting with version 24.1***

---

 - [pases.el](https://launchpad.net/pases)
 - [pelm](http://github.com/eggcaker/pelm) - Command line installer; using php.
 - [plugin.el](http://gmarceau.qc.ca/plugin.el)
 - [straight.el](https://github.com/raxod502/straight.el) - Recent and experimental, has not reached 1.0 release yet.
 - [use-package.el](http://www.emacswiki.org/emacs/UsePackage)
 - [XEmacs package manager](http://www.xemacs.org/Documentation/packageGuide.html)

package has been included in the Emacs trunk. epkg is not ready yet and also currently not available. At least install-elisp, plugin and use-package do not seem to be actively maintained anymore.

I have created a git [repository](https://github.com/emacsmirror/all-package-managers) containing all these package managers as submodules.

**Some utilities that might be useful**

Package managers could use these utilities and/or they could be used to maintain a mirror of packages.

 - [date-calc.el](http://www.emacswiki.org/emacs/date-calc.el) - Date calculation and parsing routines.
 - [ell.el](http://www.damtp.cam.ac.uk/user/sje30/emacs/ell.el) - Browse the Emacs Lisp List.
 - [elm.el](http://github.com/tarsius/elm), [elx.el](http://github.com/tarsius/elx), [xpkg.el](http://github.com/tarsius/xpkg) - Used to maintain the [Emacsmirror](http://www.emacsmirror.org).
 - [genauto.el](http://www.gnufans.net/~deego/emacspub/lisp-mine/genauto/) - Helps generate autoloads for your elisp packages.
 - [inversion.el](http://www.emacswiki.org/emacs/InVersion) - Require specific package versions.
 - [loadhist.el, lib-requires.el, elisp-depend.el](http://www.emacswiki.org/emacs/LibraryDependencies) - Commands to list Emacs Lisp library dependencies.
 - [project-root.el](http://www.shellarchive.co.uk/content/lisp/project-root.el) - Define a project root and take actions based upon it.
 - [strptime.el](http://www.emacswiki.org/emacs/strptime.el) - Partial implementation of POSIX date and time parsing.
 - [wikirel.el](http://www.emacswiki.org/emacs-en/wikirel.el) - Visit relevant pages on the Emacs Wiki.

**Discussions about the subject at hand**

 - [emacs-devel 20080801](http://article.gmane.org/gmane.emacs.devel/101927)
 - [comp.emacs 20021121](http://groups.google.com/group/comp.emacs/browse_thread/thread/696d4ba8809ff258)
 - [RationalElispPackaging](http://www.emacswiki.org/emacs/RationalElispPackaging)

**The question (finally)**

So - I would like to know from you what you consider important/unimportant/supplementary etc. in a package manager for Emacs.

***Some ideas***

 1. Many packages (the [Emacsmirror](http://www.emacsmirror.org) provides that largest available collection of packages, but there is no explicit support in any package manager yet).
 2. Only packages that have been tested.
 3. Support for more than one package archive (so people can choose between many/tested packages).
 4. Dependency calculated based on required features only.
 5. Dependencies take particular versions into account.
 6. Only use versions that have been released upstream.
 7. Use versions from version control systems if available.
 8. Packages are categorized.
 9. Packages can be uninstalled and updated not only installed.
 10. Support creating fork of upstream version of packages.
 11. Support publishing these forks.
 12. Support choosing a fork.
 13. After installation packages are activated.
 14. Generate autoload files.
 15. Integration with Emacswiki (see wikirel.el).
 16. Users can tag, comment etc. packages and share that information.
 17. Only FSF-assigned/GPL/FOSS software or don&#39;t care about license.
 18. Package manager should be integrated be distributed with Emacs.
 19. Support for easily contacting author.
 20. Lots of metadata.
 21. Suggest alternatives before installing a particular package.

***I am hoping for these kinds of answers***

 - Pointers to more implementations, discussions etc.
 - Lengthy descriptions of a set of features that make up your ideal package manager.
 - Descriptions of one particular desired/undesired feature. Feel free to elaborate on my ideas from above.
 - Surprise me.

What do you expect from a package manager for Emacs?

Whenever I run `conda install/remove/update &lt;package&gt;`, it tells me it&#39;s &quot;Solving environment&quot; for some time before telling me the list of things it&#39;s going to download/install/update. Presumably it&#39;s looking for dependencies for `&lt;package&gt;`, but why does it sometimes *remove* packages after doing this operation? For example, as I was trying to install Mayavi, it decided it needed to remove Anaconda Navigator. 

Furthermore it does not provide an option to perform only a subset of the suggested operations. Is there a way to specify that I don&#39;t want a package removed?

What does conda do when &quot;solving environment&quot;

So how does the &quot;[replace][1]&quot; property work with [composer][2]? I have read the composer document but still not understand it. Searching for more info hasn&#39;t answered my questions.

When I look at the composer.json file on [Laravel/Framework][3] on github. I can&#39;t see how replace will work. Can someone explain to me how this works? And what the variable &quot;self.version&quot; will equal to?

  [1]: http://getcomposer.org/doc/04-schema.md#replace
  [2]: http://getcomposer.org/
  [3]: https://github.com/laravel/framework/blob/master/composer.json

How does the &quot;replace&quot; property work with composer?

I know how to use rpm to list the contents of a package (`rpm -qpil package.rpm`). However, this requires knowing the location of the .rpm file on the filesystem. A more elegant solution would be to use the package manager, which in my case is YUM. How can YUM be used to achieve this?

How to list the contents of a package using YUM?

If I&#39;m using Alpine 3.8, how can I add a specific package from the Alpine Edge repository? Is this even supported? There is no equivalent of backports, from what I can see.

I want to add the new version of this: https://pkgs.alpinelinux.org/package/edge/community/armhf/librdkafka

And not the older version in the 3.8 repo:
https://pkgs.alpinelinux.org/package/v3.8/community/s390x/librdkafka

All Package Managers Solutions on Gang of Coders

Total of 26 Package Managers Solutions