3 ms·
Some feedback on the page. I think I'm squarely in the target audience. I'm familiar with Heroku Buildpacks. I wrote my own tool to generically build projects b
by antoncohen 6y ago
Some feedback on the page. I think I'm squarely in the target audience. I'm familiar with Heroku Buildpacks. I wrote my own tool to generically build projects by detecting languages, build tools, etc. I based the detection of Heroku Buildpacks. And I packaged the tool into builder images.
But reading this page, I can't tell what Paketo Buildpacks do, when I'd use them, or how I'd use them. Usage examples would probably help. Some clear call out of "You want to do X, we solve that".
For examples of why this page is hard to understand, see these sections:
- What are Buildpacks? - Basically says "CNCF Buildpacks are an evolution of buildpacks"
- What are Paketo Buildpacks? - Basically says "they use Cloud Native Buildpacks"
- Why Paketo Buildpacks? - Basically says "unlike other buildpacks, we are better buildpacks"
Even knowing what buildpacks are in general, and building container build automating for a living, I can't tell if I have a use for Paketo Buildpacks.
- hardwaresofton 6y ago+1 I am very much not the target audience (I don't really use build packs much), but I'm interested in the space (I am toying with the idea of running a PaaS) and it is very unclear to me why I would use this project instead of pack[0]. Currently I'm just defaulting to thinking that this is Cloud Foundry's attempt to enter the buildpack space, since standardization of the buildpack ecosystem (and adherence to set standards) lowers the bar of entry for them. [0]: https://buildpacks.io/docs/install-pack/ https://buildpacks.io/docs/install-pack/
- dwillist 6y agoThanks for the feedback about clarity. Paketo Buildpacks are supposed to be used with pack. Basic equation is (Pack) + (Cloud Native Buildpacks) = (OCI image). Packeto Buildpacks are an option for the Cloud Native Buildpacks piece.
- hardwaresofton 6y agoNo problem, apologies for my misunderstanding of where Cloud Foundry was in the space, had no idea it was involved so much in the initial buildpacks breakout & standardization. I understand very well where packeto fits in the buildpack space now, and how it integrates with `pack` itself.
- jacques_chester 6y agoCloud Foundry has had buildpacks for 6 years or so, initially soft forks of Heroku buildpacks (I worked on these for some time). The standardisation came about because Heroku and Cloud Foundry folks teamed up. In terms of your specific question: pack is a CLI tool for using buildpacks to generate images. Paketo is a supported collection of such buildpacks. An analogy might be that pack is a compiler, Paketo is a standard library.
- hardwaresofton 6y agoThanks very much for replying and clearing up my misunderstanding. This makes a lot more sense now and I understand exactly where Packeto sits.
- jacques_chester 6y agoHappy to help.