allow pkgin packages to be specifed with versions#6229
Closed
jeremyherbert wants to merge 1 commit into
Closed
Conversation
Member
|
this request needs a rebase |
Contributor
|
@jeremyherbert this PR should be rebased to target Meanwhile, this PR should be closed. |
Author
|
I'm sorry @amenonsen , I created this patch request over a year and a half ago; I'm no longer able to access the system I used to test this. |
ansibot
added
feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pkgin module does not allow one to specify a specific package version. This is a big problem if you want to install a package that exists as multiple versions like erlang, which has both "erlang-16.1", "erlang-15.1.3.1" on my Joyent SmartOS distribution.
A fix is provided.