[Buildroot] [PATCH 1/1] package/systemd: bump version to 242

James Hilliard james.hilliard1 at gmail.com
Tue Jun 11 22:37:20 UTC 2019


On Tue, Jun 11, 2019 at 4:09 PM Arnout Vandecappelle <arnout at mind.be> wrote:
>
>
>
> On 11/06/2019 00:55, James Hilliard wrote:
> > On Mon, Jun 10, 2019 at 11:51 AM Jan Kundrát <jan.kundrat at cesnet.cz> wrote:
> >>
> >> This is not a simple bump for people who use systemd-networkd (or
> >> timesyncd, or resolved, or ...). On a build-from-scratch, these services
> >> won't be enabled anymore. A recent change now apparently requires people to
> >> run `systemctl prepare-all` [1] to re-create symlinks which enable these
> >> services.
> >>
> >> This makes cross-building more complex, so I filed an issue upstream [2].
> > Hopefully this fixes it:
> > https://github.com/systemd/systemd/pull/12769
>
>  I actually agree with the analysis made upstream, that it's better to call
> systemctl --root=/path/to/it preset-all rather than maintaining two code paths
> that do the same thing. Yes, it means we need to build a minimal host-systemd to
> get systemctl, but I don't see that as a big showstopper.
Yeah, I understand their reasoning, it just seems like overkill for a
few symlinks.

The build system may provide a way to do build a systemctl for the host as part
of the target build using this:
https://mesonbuild.com/Cross-compilation.html#mixing-host-and-build-targets
Not sure how difficult that would be though.
>
>  Regards,
>  Arnout
>
> >>
> >> Cheers,
> >> Jan
> >>
> >> [1] https://github.com/systemd/systemd/blob/v242/NEWS#L223
> >> [2] https://github.com/systemd/systemd/issues/12767
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >



More information about the buildroot mailing list