In order to easily make constraints available to consumers of generated SPK package files, include the used constraints file with both "interpreter" and "packages" SPK files (with different file names so that they don't overwrite each other in some deployment scenarios).
In order to easily make constraints available to consumers of generated SPK package files, include the used constraints file with both "interpreter" and "packages" SPK files (with different file names so that they don't overwrite each other in some deployment scenarios).