### What needs to get done Currently, one can use `adopt-info` to set a snap's version information via something like: ``` adopt-info: foo <snip> parts: foo: override-pull: | craftctl set version=$(git describe --long) ``` It would be very useful if the version of a component could be set in a similar fashion. For instance, ``` adopt-info: foo <snip> parts: foo: override-pull: | craftctl default craftctl set version=$(git describe --long) override-build: | craftctl default bar_ver=$(basename "${CRAFT_PART_INSTALL}/<...>/baz") craftctl set bar.version="$bar_ver" organize: <...>: (component/bar)/<...> <snip> components: bar: version: adopt-info <snip> ``` ### Why it needs to get done This would be useful in a variety of use-cases. For instance, if a component is created from some debian package, it may be more useful for that debian package's version to be the component's version, rather than the version of the snap itself. A specific example would be with kernel snaps, where the component's version is more usefully understood as being related directly to the kernel ABI it was built against (immediately indicating whether a particular component will work with a particular kernel snap). At the very least, this change makes the version maintenance burden for components a lot simpler -- I would no longer need to manually check the version for a component, where the valid version is even less obvious a priori in the case of kernel snaps.