Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC 0069] Support Stack Buildpacks #501

Closed
ekcasey opened this issue Jan 14, 2021 · 3 comments
Closed

[RFC 0069] Support Stack Buildpacks #501

ekcasey opened this issue Jan 14, 2021 · 3 comments

Comments

@ekcasey
Copy link
Member

ekcasey commented Jan 14, 2021

RFC 0069
buildpacks/rfcs#111

buildpacks/spec#177
buildpacks/spec#178

@natalieparellano
Copy link
Member

natalieparellano commented Mar 31, 2021

Blocked on #530 and (I think?) #471

This issue could probably benefit from being broken down into smaller issues, and having an associated spec PR at least in draft status (maybe the spec PR could also be broken down).

Some thoughts on how this could be chunked based on the existing draft PR to lifecycle (#410):

  • Static satisfaction (via stack.toml) of statically required (via buildpack.toml) mixins <- pack does this today, need to add to lifecycle
    * Dynamic satisfaction (via build plan) of dynamically required (via build plan) mixins <- existing draft PR for stack buildpacks does this
    * Dynamic satisfaction (via build plan) of statically required (via buildpack.toml) mixins <- seems this should be easier to add if we've done the first two
  • Static satisfaction (via stack buildpacks' buildpack.toml) of statically required (via buildpack.toml) mixins
  • Static satisfaction (via stack OR stack buildpacks' buildpack.toml) of dynamically required (via build plan) mixins
  • A way for stack buildpacks to disable cache on rebuilds
  • A way for stack buildpacks to skip taking new snapshots on subsequent re-runs
  • A way for stack buildpacks to exclude/include parts of the snapshot
  • extend phase
  • Probably other things missing here

@jabrown85 what do you think?

@natalieparellano
Copy link
Member

Also might be good to think about which of these issues could be parallelizable.

@natalieparellano
Copy link
Member

@natalieparellano natalieparellano removed this from the lifecycle-0.12.0 milestone Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants