Skip to content

Commit ba6fa1a

Browse files
committed
Add installation names and order to CNB RFC
1 parent 6d6bd81 commit ba6fa1a

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

toc/rfc/rfc-draft-add-cnbs.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -196,9 +196,12 @@ buildpacks are shimmed. In such an event, a follow-on RFC will describe this
196196
work.
197197

198198
The CNBs will initially be opt-in for CF Deployment operators via an
199-
experimental ops file. Once the buildpacks have reached a suitable level of
200-
maturity and stability, they will be added to the default
201-
set of buildpacks installed as part of CF Deployment.
199+
experimental ops file. When installed, the Paketo buildpacks will follow a
200+
different naming convention than the v2 buildpacks (e.g. `paketo_ruby` instead
201+
of `ruby_buildpack`) and will be installed with a lower detect order than the
202+
v2 buildpacks. Once the v3 buildpacks have reached a suitable level of maturity
203+
and stability, they will be added to the default set of buildpacks installed as
204+
part of CF Deployment.
202205

203206
### Possible Future Work
204207

0 commit comments

Comments
 (0)