Closed
Description
When cargo libcnb package is run, at the end of the packaging process an example pack build command is displayed, with the aim of making it (a) easy for people to understand how to use the compiled buildpack, (b) to save them having to type all of the CLI arguments/paths by hand.
Prior to #575, this example pack build command used relative paths to the buildpack, however, it now uses absolute paths, eg:
💡 To test your buildpack locally with pack, run:
pack build my-image-name \
--buildpack /Users/emorley/src/buildpacks-python/target/buildpack/x86_64-unknown-linux-musl/debug/heroku_python \
--path /path/to/application
(ie: the /Users/emorley/src/buildpacks-python/target/buildpack/x86_64-unknown-linux-musl/debug/heroku_python)
We should switch back to relative paths to make the shown command shorter and easier to see that the files have actually been saved inside the source dir at a quick glance.