Steen Schmidt Posted February 17, 2015 Report Share Posted February 17, 2015 Hi, I've noticed that packages will install without complaint when all dependency packages can be found, but even if these dependencies are of lesser version than the minimum required as specified by the top-level package. I thought that VIPM would complain during install of such a package, if the minimum requirements of dependency versions weren't achieved? Why else include version in the dependencies list? Example: A.vip specifies a dependency 'B.vip >= 3.0.0.15'. A.vip will install happily even if B.vip is only available in version 2.0.0.10 for instance. I'd expected VIPM to tell me "Missing dependency" in this case. Cheers, Steen Link to comment Share on other sites More sharing options...
Ashish Posted March 2, 2015 Report Share Posted March 2, 2015 Steen, We were not able to reproduce the behavior. We tried using the available packages in VIPM and setting up the dependency for version mismatch. Package was built successfully and during the package installation, we received the message to update the dependent package and that was also installed successfully. Can you help understand your scenario better? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.