On Mon, Nov 4, 2024 at 11:22 AM Thorsten Kukuk wrote:
> Ah, I forgot about that new utility during my vacation...
> But updatectl does not solve my problems, see above.
> It's still centric about this "there is a base OS image and all
> extensions have the same image version", even if it has a ni
Hi Adrian,
On Thu, Oct 31, 2024 at 5:50 PM Adrian Vovk wrote:
>
> On Thu, Oct 31, 2024 at 11:30 AM Thorsten Kukuk wrote:
> >
> > Hi Adrian,
> >
> > On Thu, Oct 31, 2024 at 3:43 PM Adrian Vovk wrote:
> > >
> > > Hi Thorsten,
> > >
> > > If I understand correctly, you're looking for a way to dist
Hi Thorsten,
If I understand correctly, you're looking for a way to distribute sysexts
such that they can be enabled/disabled, and they're updated in lock step
with each other and the base OS. Is that correct?
If so, you're looking for Optional Features [1], which will release with 257
Best,
Adr
Hi,
I'm currently working on integrating systemd-sysext in MicroOS.
For this I created several sysext images with different tools (e.g.
"gcc", "debug", ...) which I can add in parallel.
Which, besides some problems with SELinux and transactional-update, works.
Now the idea is to use systemd-sysu
