[elbe-devel] [elbe-users] ELBE v15.1

Thomas Weißschuh thomas.weissschuh at linutronix.de
Tue Sep 3 09:49:03 CEST 2024


Hi Manuel,

On Fri, Aug 30, 2024 at 09:14:51PM GMT, manut wrote:
> Hi Thomas,
> 
> On Fri, Aug 30, 2024 at 12:53:36PM +0200, Thomas Weißschuh wrote:
> > Dear ELBE community,
> > 
> > I'm happy to annouce the release of ELBE v15.
> > Please find the release notes below:
> 
> thanks for taking care on elbe :)

You're welcome :-)

> > Deprecations and Removals
> > -------------------------
> 
> I did not expect feature removals on a minor upgrade..

As indicated, I do think that nobody should be affected by these
removals.

> > - The *internal* command `elbe adjustpkgs`.
> > - The *internal* command `elbe buildchroot`.
> 
> I used 'elbe buildchroot' often directly in containers
> triggered by a CI. This was quiet useful. But meanwhile
> I use mkosi for this, so it does not hurt me.

This sounds reasonable, but I'm not sure if other users besides people
intricately familiar with elbe are doing the same.
It's not described in any way in the prose documentation and completely
bypasses the documented initvm machinery and architecture.
It also has drawbacks around license reporting and SBOM generation that
a user would need to be aware about.

FYI I intend to make the initvm abstraction more generic so for the
container usecase the local machine can be used as "initvm".
Also today its possible to use a normal qemu process instead of a full
libvirt VM as initvm.

> However for me it was no internal command. There was a
> even a user visible man-page that described the command.

All manpages were user visible. Even those for commands like
fetch_initvm_pkgs, xsdtoasciidoc and daemon. So that is a limited reason :-)
And many of those removed commands were broken for quite some time.
As they are not part of the regular elbe workflow I deemed it better to
remove them instead of spending time trying to fix them or having users
getting confused while looking at the docs.

> Just wanted to mention, that there might be use-cases out
> there for still having those commands.

If anybody wants them back, they can always be reintroduced.


Thomas


More information about the elbe-devel mailing list