toggle quoted messageShow quoted text
Custom buildpacks (v2) can be installed in airgapped and enterprise CF. You convert the buildpack and it’s dependencies into a zip file and the CF admin installs it for all users to share, like you would upgrade a buildpack from the core CF team.
Paketo buildpacks (v3) — your own plus upstream — are baked into your builder Docker image, so again you have control over what buildpack you are using across all apps.
Hi Dr. Nic,
thanks for your reply and the links shared to the new buildpacks and the tutorial. As I’d like to use the buildpack within an enterprise context such custom buildpack would be a good starting point, but the ultimate goal
would be to get it listed as part of this:
If I get you right, the CF core team/paketo team might be the right contacts to talk to about this topic to get a Rust buildpack eventually a core/system buildpack? Are you able to share some contact details to start
the communication with the right audience straight away?
Thanks in advance.
Skipping the question of “core buildpacks” which is a good one but I can’t answer it.
I can point you to two paths for authoring Buildpacks, depending on which CF your using.
Newer CF/kubernetes CF uses Paketo buildpacks
https://paketo.io/ which are implementations of the Cloud Native Buildpacks project
https://buildpacks.io — the latter page has a tutorial for creating a buildpack; and the former is a collection of buildpacks. If you want your Rust buildpack to be “core” one day, cargo cult the core team/paketo team’s buildpacks
rather than implement yours from scratch.
If you’re on an older CF, and using the older buildpacks then yes you can create a Rust buildpack, but it will never be included in “core” — the core team/paketo team is solely working on the new set of buildpakcs above. I wrote some tutorials
for creating the older buildpacks; but I hesitate to recommend them since they are “the old way” :)
+61 437 276 076