Jump to content

Fine grained control of package dependencies

Recommended Posts

Dear all,

I hope that the following question has not already been asked.

Anyways, imagine I have package B which depends on package A. Imagine that packages B and A are both at version 1.0.0.x . Now assume that I bumped package A version to 2.0.0.x and I broke API compatibility so that Package B v1.0.0.x stops working with Package A v2.0.0.x. Is there a way in Package B build specification to specify a package dependency such that Package B requires Package A to be at version >=1.0.0.x and < ? In this manner, one would prevent the user who installs Package B (which has never been upgraded to be compatible with Package A v2.0.0.x) from ending up in situations where Package B is broken.

I hope I managed to be sufficiently clear.

Thanks in advance for any clarification.




Link to comment
Share on other sites

Join the conversation

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

Reply to this topic...

×   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.

  • Create New...

Important Information

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