Hey @pombredanne , Looks good issue, I would like to learn more about it and maybe contribute to it, Shall I work on it If there's no one else working on the same?

@pombredanne I'm interested in extending the project to handle the buildpack.toml manifest and wanted to check in to ensure I understand the full scope of the task.

Could you please provide a bit more context regarding:
The specific parts of the project that need this support?
Any particular edge cases or functionality you'd like to be considered?
How you envision the buildpack.toml information being utilized in the system (e.g., dependency handling, build steps)?

Hello @pombredanne This is my analysis, I've opened a pull request trying to implement it, kindly review it when you have time.

1. https://buildpacks.io/docs/reference/config/buildpack-config/
   This is the format spec for buildpack files

2. few test files used:

For Paketo buildpacks-
https://github.com/paketo-buildpacks/dotnet-execute/blob/main/buildpack.toml
https://github.com/paketo-buildpacks/git/blob/main/buildpack.toml
https://github.com/paketo-buildpacks/java-memory-assistant/blob/main/buildpack.toml
https://github.com/paketo-buildpacks/opentelemetry/blob/main/buildpack.toml
https://github.com/paketo-buildpacks/pipeline-builder-canary/blob/main/buildpack.toml

For heroku buildpacks-
https://github.com/heroku/heroku-buildpack-php/blob/main/buildpack.toml
https://github.com/heroku/heroku-buildpack-java/blob/main/buildpack.toml

@NucleonGodX see PR for comments