search

buildpacks / pack

CLI for building apps using Cloud Native Buildpacks
https://buildpacks.io
Apache License 2.0
2.56k stars 286 forks source link

More Clear Info on Buildpacks #200

Closed jamesward closed 4 years ago

jamesward commented 5 years ago

It should be clear where the buildpacks in a builder image come from so that people know where to file bugs / find the source.

ahmetb commented 5 years ago

Specifically https://hub.docker.com/r/heroku/pack & https://hub.docker.com/r/heroku/buildpacks.

sclevine commented 5 years ago

CC: @hone @jkutner for Heroku images.

(For CF, see: https://hub.docker.com/r/cloudfoundry/cnb)

ekcasey commented 5 years ago

One possible path forward would be to allow builder authors to optionally supply links to the buildpack source as part of the builder configuration. That way pack inspect-builder could display that information.

hone commented 5 years ago

I'm 👍 on having buildpacks being able to specify this along with description and other metadata that is important. The registry will take advantage of this data too.

zmackie commented 4 years ago

Do we think this might need an RFC or would it be a platform specific thing?

jromero commented 4 years ago

Given buildpack authors from various avenues would provide this information I believe this should be spec'd.

My initial thought is that this could live in a buildpack.toml similar to how project.toml has source and documentation urls. Builders, buildpackages, and thereby platforms, can then leverage this information.

jromero commented 4 years ago

Closing this as an RFC has been filed. Once that is accepted we can implement that as a feature which would satisfy this issue.

RFC: https://github.com/buildpacks/rfcs/pull/55