You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current set of Paketo buildpacks fall into 2 distinct camps when it comes to the toolkits used in their development: those using libcnb and libpak, and others using packit. Having this dual toolkit ecosystem confuses our users and contributors and may act as a barrier to entry in some cases. In this discussion, I'd like to start a conversation to help us move towards reconciling these differences.
Here are a topics that might help us to get started:
Outline the philosophies behind the 2 toolkits we use.
Identify the goals we collectively share in using these toolchains.
Identify the smallest step we can take to move towards a converged toolkit.
Identify areas where we already have agreement but maybe don't know it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The current set of Paketo buildpacks fall into 2 distinct camps when it comes to the toolkits used in their development: those using
libcnb
andlibpak
, and others usingpackit
. Having this dual toolkit ecosystem confuses our users and contributors and may act as a barrier to entry in some cases. In this discussion, I'd like to start a conversation to help us move towards reconciling these differences.Here are a topics that might help us to get started:
Beta Was this translation helpful? Give feedback.
All reactions