fix(pebble): place pebble in a separate location (#528)
The context here is that starting from Ubuntu 24.04, the 'base-files' package
(and related chisel slices) provides "bin" as a symlink to "usr/bin". This
breaks the previous "phantom" pebble part because it created "bin" as a regular
directory which then conflicts with the symlink.
Moving forward, the pebble binary is now placed in ".rock/bin/". This way we
won't get further collisions and this reflects the fact that the location of
the binary is, and should be seen, as an implementation detail.
1101844...
by
David Andersson <email address hidden>
fix(flask): don't enforce definition of base, build-base and platforms (#529)
Those slices are currently fragile due to the ongoing time_t changes. Instead,
use coreutils_bins because it has fewer dependencies (but still some) and is
more stable. The purpose of the test is just to check that we can cut any slices
at all for base devel anyway.
chore: force build-base and platform on flask examples
The problem is this: the flask extension currently adds a 'build-base' if the
'base' is 'bare' but the 'build-base' is undeclared, and a 'platforms' entry
if it's missing, but this behavior breaks with the new version of
craft-application because the BuildPlanner processes the yaml _before_ the
extensions are applied, and the planner cannot work without a build-base or
platform description.
The extension behavior of adding a 'build-base' and a 'platforms' item needs
to be reviewed: we probably don't want to support this. In the meantime,
this commit fixes only the projects that are executed in spread.
The brunt of the update is updating usages of platform/build-for to the build
plan. This largely affects the image and package services, but the semantics
should be unchanged because it's the same data just delivered differently.
