This enables a buildpack to become entirely composable. Great work by @salsify
For example. Am currently using this to enable deploying a node.js app that depends on cairo.
Note, as some of the existing heroku buildpacks completely override previously set ENV variables at compile time, tweaks may be needed in other buildpacks themselves.
allow buildpacks to export environments
pass the dir along
any chance to integrate this pull request?
(Or equivalently) any workaround to pass enviroment variable between buildpacks?
(Unfortunately) any library which is requiring the usage of pkg-config which need to be available at compilation time will require hack on the main buildpack.
It is specifically an issue for nodejs binded libraries
I'm running into this trying to use the npm package nodelua. The lua buildpack runs first, but has no way to pass on environment variables to the next buildpack.
I wonder if we could utilize the new .profile.d scripts to enable this functionality.
(not so new anymore) https://devcenter.heroku.com/articles/profiled
Alas, not as currently implemented, since the paths will be different at build- and runtime.
Adding env export for next buildpack
This is taken from ddollar#11
I am testing to see if this fixes the collectstatic issue experienced when deploying to heroku (possibly PYTHONPATH not currently set for python buildpack)
Sorry for the delay. If you rebase this I'd be happy to merge.
All things being equal between this and #18, I have multiple buildpacks relying on #18's export behavior. (@davidjrice - do you have / know of buildpacks relying on this?)
(I'm slightly partial to the exports living outside bin, as they may be created dynamically; not that bin precludes this though.)