source of binaries listed in manifest - part II

[luisapace]

Hi, my team would like to use binary-buildpack 1.0.17 and to approve that I've to analyze it's source code and the code of its dependencies chain, so be sure that they don't have problematic licenses.

I've some questions:

1. in the https://github.com/cloudfoundry/binary-buildpack/blob/v1.0.17/src/binary/vendor/github.com/cloudfoundry/libbuildpack/fixtures/manifest/standard/manifest.yml

I see reference to:
jruby 9.3.4
jruby 9.3.5
jruby 9.4.4

but I cannot found their source on the net, those versions seem to not exist, could you help me please?

2. in the

https://github.com/cloudfoundry/binary-buildpack/blob/v1.0.17/src/binary/vendor/github.com/cloudfoundry/libbuildpack/packager/fixtures/bad/manifest.yml

AND

https://github.com/cloudfoundry/binary-buildpack/blob/v1.0.17/src/binary/vendor/github.com/cloudfoundry/libbuildpack/packager/fixtures/good/manifest.yml

I see reference to:

ruby 1.2.3

but I cannot found its source on the net, this version seems to not exist, could you help me please?

3. in the

https://github.com/cloudfoundry/binary-buildpack/blob/v1.0.17/src/binary/vendor/github.com/cloudfoundry/libbuildpack/packager/fixtures/modules/manifest.yml

I see reference to:

php 1.6.1

but I cannot found its source on the net, this version seems to not exist, could you help me please?

Some of those packages have been associated with different versions in the URI.

Could you please clarify me all those things?

Thanks a lor again

Thanks.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/158288813

The labels on this github issue will be updated when the story is started.

[sclevine]

Everything in fixtures is test data that isn't included in the buildpack. Those versions don't exist, as you've noticed.

[luisapace]

Thanks a lot !