Implement carmel pin Module@version #39
Merged
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.
Imagine you have cpanfile:
and the snapshot has the version 4.00.
You can update to the latest version available from CPAN with
carmel update JSON
. Let's say you don't want the version on CPAN today, and want to pin to a specific version. You can update cpanfile:This works fine, but then you need to unpin every time you update to newer versions.
The new
carmel pin
command allows you to keep the version specification incpanfile
(so that future run ofcarmel update
will update to the latest), while pinning to the specified version, rather than whatever is the latest on CPAN when you run it.carmel pin JSON@4.04
is essentially the same as:cpanfile
to haverequires 'JSON', '== 4.04';
carmel install
to pin the JSON version in the snapshotcpanfile
torequires 'JSON', '4';