Hi, Supporting multiple versions at the same time will be required as soon as a SCons release breaks compatibility. If you want your older product sources built with an old SCons to keep building, you need to keep this old Scons available for them. And you would update your build system in your product develop branch to take the new SCons into account. You could argue that all product branches must be updated as well. But what about tags, which you may need to checkout again and rebuild?
The only solution if such api change occurs and multiple versions installed at the same time are not supported would be to check SCons into the product repo. But for all products which didn't start this way from the very beginning, it's too late, and they would get stuck. Unless virtual env is the official and documented method to have multiple versions in production? (never used it, don't know exactly how it's supposed to be used). -- Alexandre Feblot > Le 6 mai 2016 à 12:34, anatoly techtonik <techto...@gmail.com> a écrit : > > On Mon, Mar 28, 2016 at 2:40 AM, Jason Kenny <dragon...@live.com> wrote: >> I am not sure we have a need to support more than on install directly. I >> will defer if someone feels this needs to support, however every case I have >> seen installing one version of SCons is enough. I only ever used more than >> on version of SCons at a time to help me test stuff in Parts. I could easily >> have done this with virtual env as well. >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
