Work on RVM 2.0 has started, check the plan here: https://docs.google.com/document/d/1xW9GeEpLOWPcddDg_hOPvK4oeLxJmU3Q5FiCNT7nTAc/edit?usp=sharing
To be able to do the RVM 2.0 work we need to stop working on RVM 1.x - this means no more feature requests will be accepted. Development on RVM 1.x will continue to provide bugfixes and support for new ruby versions as long as RVM 2.0 will not become stable. RVM is an open source project so any contributions are welcome - including new features pull requests - as long as they keep compatibility and do not break anything.
The following files need to be updated to add support for a new version of an already supported Ruby interpreter. Please follow the patterns used in those files and add entries in the appropriate location. #4366 is a good example of the required changes.
config/known
- update existing entry when minor version released
- add new entry when major version released
config/known_strings
- add an entry for the new version releasedconfig/db
- update only for stable releasesconfig/md5
- add new line withmd5
hash of the archiveconfig/sha512
- add new line withsha512
hash of the archive
When listing interpreter source make sure that you link to the smallest archive variant (usually .bz2
).
When release package does not include md5
or sha512
hashes you should download the source package and calculate it yourself.
One of the ways to do that would be to use openssl
command:
openssl dgst -sha512 FILE
openssl dgst -md5 FILE
To test a local copy of RVM for development purposes simply enter the folder with the source and install it:
./install && rvm reload
If you don't want to destroy your working environment, you can select a different destination folder and easily switch between them:
./install --path ~/.rvm-dev
rvm switch ~/.rvm-dev # development version
rvm switch ~/.rvm # production version