Re: [OE-core] [PATCHv2 0/5] systemd split networkd package

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2024-12-12 at 16:55 +0100, Adrian Freihofer via lists.openembedded.org wrote:
> v2 fixes the build warning
> 
> First of all, this patch series fixes a bug in systemd.bbclass that
> forces service files with an Also= relationship to be in the same
> package. This may often be the case, but as long as the RDEPENDS
> between the packages are set correctly, it is no problem to distribute
> the service files over several packages.
> 
> If service files referenced with Also= are no longer automatically added
> to the list of FILES, build errors caused by unpacked files are
> expected. A bitbake world has shown that there are only two recipes in
> oe-core that use automatic packing: busybox and dropbear. There are 2
> patches that fix this.
> 
> Also= relation are probably most often used for sockets. Consequently
> the systemd.bbclass should also allow to split socket files into
> separate packages. However, that's proably practically not used and
> would cause tons of packaging errors. Therefore the automatic packaging
> feature for sockets is not changed.
> 
> The latest patch splits systemd-networkd into its own package. This adds
> a little extra complexity, but splitting systemd into packages is a good
> step towards making Yocto more usable in binary form.

The changes to busybox and dropbear suggests there are some
considerations needed here from a migration perspective as people
upgrade past this change? Is there some documentation we should be
adding to the migration guide along with these changes?

Cheers,

Richard