Thanks for raising the issue here as well, Aaron, and I'm glad to see we
got a fix figured out for that buildpack. I've added a story (
https://www.pivotaltracker.com/story/show/116149519) to the Buildpacks
tracker to document more clearly what bits are captured from the
staging-task container into the droplet, so that other buildpack authors
have more definitive guidance on how to compile and arrange vendored
dependencies.

Best,
Eric

On Mon, Mar 21, 2016 at 2:08 PM, aaron_huber <aaron.m.huber(a)intel.com>
wrote:

I've got a few customers using the Sourcey buildpack along with
Perl/Mojolicious and we've found that it is non-functional when used on
Diego cells. It continues to work fine on DEA. Has anyone been successful
at deploying with this buildpack on Diego, or does anyone have any
suggestions on what might be different that's causing it to break?

I've posted on an issue in the buildpack repo but the developer could use
some help with documentation or some tips on what might be different.

https://github.com/oetiker/sourcey-buildpack/issues/1

Aaron Huber
Intel Corporation




--
View this message in context:
http://cf-dev.70369.x6.nabble.com/Sourcey-buildpack-not-working-on-Diego-tp4275.html
Sent from the CF Dev mailing list archive at Nabble.com.