Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Support custom stacks #132

Open
ghost opened this issue Sep 28, 2022 · 1 comment
Open

Support custom stacks #132

ghost opened this issue Sep 28, 2022 · 1 comment

Comments

@ghost
Copy link

ghost commented Sep 28, 2022

Is there anything preventing this buildpack from supporting custom stacks? I'm working on a custom stack based on RHEL and I get this error when trying to include the node buildpack in my custom builder:

ERROR: validating buildpacks: buildpack paketo-buildpacks/node-module-bom@0.4.2 does not support stack com.my.custom.stack

I think a similar change is being implemented for the go buildpack at the moment.
paketo-buildpacks/go#651 (comment)

Essentially, I'm asking for these lines be added to the end of buildpack.toml and metadata.dependencies be updated accordingly:

[[stacks]]
  id = "*"
@sophiewigmore
Copy link
Member

sophiewigmore commented Sep 29, 2022

Hey @ben-galusha, I think it depends on if the CycloneDX BOM tool that the buildpack installs will work on any stack. Buildpacks that provide dependencies such as this one are difficult to move over to the * stack because it implies that the dependency can work on anything. Maybe it'll just work but some investigation is needed.

For example, the Cpython buildpack provides python. It recently moved over to the * stack but had a bunch of new logic implemented to compile the python dependency at build-time depending on the stack to guarantee compatibility.

All this is to say, I don't think we can just move this buildpack to the * stack, it will depend on how the dependency needs to be handled! Perhaps @paketo-buildpacks/nodejs-maintainers have more insight into a plan for this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant