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
This issue is for adding venv-like environments to mpm. I'm going to call them "collections" instead of environments since mpm -e is already being used ;)
The idea in this setting is that a collection is a nickname for a particular collection of packages, which you can then easily enable/disable in order to add/rm the paths to all of those installations.
A few notes:
mpm init -c colname enables a collection called colname (creating one if it doesn't exist), which means rmpaths for the previous collection (e.g., default), and adding paths for the new collection
every user has a default collection, so that mpm init is short-hand for mpm init -c default
each collection gets its own folder inside the user's default install directory (e.g., assuming the install directory is mpm-packages, then all packages for the colname collection should be installed to mpm-packages/mpm-collections/colname). for easier backwards compatibility, packages in the default collection are still installed directly to mpm-packages.
mpm install -c colname (similarly for mpm uninstall) indicates to install the package to the colname collection
mpm freeze -c colname lists the packages in colname
in all cases (install, uninstall, freeze, etc.), if -c is not provided then the implied collection is always-c default, NOT the currently init'd collection. To me, this is a safer bet, since there's no easy way to specify which collection is currently enabled (unlike in venv, for example, where it's prefixed to your bash prompt)
e.g., in the following, the package tmp would be installed to the default collection, NOT the test collection, while tmp2 would be installed to the test collection and not the default collection.
>> mpm init -c test
>> mpm install tmp
>> mpm install tmp2 -c test
The text was updated successfully, but these errors were encountered:
This issue is for adding venv-like environments to mpm. I'm going to call them "collections" instead of environments since
mpm -e
is already being used ;)The idea in this setting is that a collection is a nickname for a particular collection of packages, which you can then easily enable/disable in order to add/rm the paths to all of those installations.
A few notes:
mpm init -c colname
enables a collection called colname (creating one if it doesn't exist), which means rmpaths for the previous collection (e.g., default), and adding paths for the new collectiondefault
collection, so thatmpm init
is short-hand formpm init -c default
mpm-packages
, then all packages for thecolname
collection should be installed tompm-packages/mpm-collections/colname
). for easier backwards compatibility, packages in the default collection are still installed directly tompm-packages
.mpm install -c colname
(similarly formpm uninstall
) indicates to install the package to the colname collectionmpm freeze -c colname
lists the packages in colnameinstall
,uninstall
,freeze
, etc.), if-c
is not provided then the implied collection is always-c default
, NOT the currently init'd collection. To me, this is a safer bet, since there's no easy way to specify which collection is currently enabled (unlike in venv, for example, where it's prefixed to your bash prompt)e.g., in the following, the package
tmp
would be installed to the default collection, NOT the test collection, whiletmp2
would be installed to the test collection and not the default collection.The text was updated successfully, but these errors were encountered: