Update RFC 0096 (stacks removal) to match what landed in the spec

[edmorley]

A few changes were made to what was in RFC96 when it came to update the spec: https://github.com/buildpacks/spec/pull/365

This backports those changes to the RFC to try and prevent user confusion if they use the RFC as a means of learning about targets when implementing.

Specifically:

• The io.buildpacks.distribution.* Docker labels were renamed to io.buildpacks.base.distro.*.
• The io.buildpacks.id Docker label was renamed to io.buildpacks.base.id.
• The buildpack.toml table [[targets.distributions]] was renamed to [[targets.distros]] and the versions field within it renamed to version (along with its type changing from an array to a string).

See: https://github.com/buildpacks/spec/blob/platform/0.13/platform.md#target-data

[buildpack-bot]

Maintainers,

As you review this RFC please queue up issues to be created using the following commands:

/queue-issue <repo> "<title>" [labels]...
/unqueue-issue <uid>

Issues

(none)

[edmorley]

@natalieparellano Sure - added now :-)

[edmorley]

Oh I also found one more change that was made when the spec was updated, that I've backported now:

• The versions field within [[targets.distros]] was renamed to version (along with its type changing from an array to a string).

(xref https://github.com/buildpacks/spec/issues/401)

[edmorley]

This backports those changes to the RFC to try and prevent user confusion if they use the RFC as a means of learning about targets when implementing.

To give some more context here - one of the reasons I look at the RFCs when implementing, is that they are quite prominently linked from the spec GitHub release entries: https://github.com/buildpacks/spec/releases

[edmorley]

(Me using the GitHub rebase button broke the GPG verification status of the commits, so I've squashed and manually pushed instead)

[edmorley]

It's spreading! 😆 https://github.com/buildpacks/rfcs/pull/295#discussion_r1559614121

[edmorley]

Please can I have review/merge? :-)