Andrea Vaccaro Posted November 14, 2023 Report Share Posted November 14, 2023 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 < 2.0.0.0 ? 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. Andrea Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted November 16, 2023 Report Share Posted November 16, 2023 Hi Andrea, The aim is for dragon.vipm.io to support this. Parts of it, under the hood, do already support it, but it's not yet exposed in the Package Dependencies UI. -Jim Quote Link to comment Share on other sites More sharing options...
Andrea Vaccaro Posted November 16, 2023 Author Report Share Posted November 16, 2023 Ciao Jim, thank you for the answer. Time to start get acquainted with Dragon then. looking forward it’s development andrea 1 Quote Link to comment Share on other sites More sharing options...
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.