Jump to content
  • 3

Semantic Versioning of Packages


Steven Dusing
 Share

Question

Currently you have two options for Package Dependency version constraints: >= or ==
I propose VIPM should use or allow Semantic versioning.  That way, if a dependency package has a breaking change, the dependent package can know that it is not compatible with the updated version.  This is a big missing piece to VIPM's dependency management, since it currently assumes that a package will forever be able to support future versions of all dependencies, which simply is not the case in real life, as breaking changes do happen from time to time.  Allowing for semantic versioning will help identify and prevent breaking code.
image.png.3abc8a5e7c24ecd3ea350c8adeb654af.png

image.png

Edited by Steven Dusing
updated reasoning for the feature
  • Upvote 1
Link to comment
Share on other sites

3 answers to this question

Recommended Posts

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.