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
Currently when using cargo libcnb package, it outputs the resulting buildpack into target/buildpack. This works great in the default (single arch) use case, but if you want to support multiple archs they will clobber each other. What if we put buildpack inside an arch directory? For instance:
Is exactly what Cargo does in the regular target directory. I think keeping parity with Cargo itself is worthwhile, especially when we're using the same output directory. We did this for the command line arguments as well to keep the surprise factor low.
Currently when using
cargo libcnb package
, it outputs the resulting buildpack intotarget/buildpack
. This works great in the default (single arch) use case, but if you want to support multiple archs they will clobber each other. What if we putbuildpack
inside an arch directory? For instance:target/buildpack/<mode>/<name>
->target/buildpack/<arch>/<mode>/<name>
Another alternative but could just be a good addition would be an
--out-dir
likecargo build
(though this is unstable atm).The text was updated successfully, but these errors were encountered: