Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for alternate packages in the pex that is built #5283
Currently the package(s) included in built pexes are hardcoded, which does not support a deployment model where relevant plugins are embedded in the deployed pex.
Add support for overriding the included packages.
The following command would build a pex with an embedded copy of
Late realization: the mechanics here look good, but I don't understand the purpose. Since the release script is none too repurposeable (maybe I have that wrong), it seems like we should just hard code which plugins (all?) we include in the pex. What's the driving use-case here?
As it stands, this pathway through the script has no consumers, since we're not yet building pexes in travis. I'll do a bit more design today to decide how we would want to advertise pexes to users, and then possibly land this as is or adjust it to include all plugins by default.