The alpm-srcinfo #crate in version 0.2.0 offers several improvements to this #library and #CLI for working with #SRCINFO files found in the #package source repositories of #ALPM based packages.

https://crates.io/crates/alpm-srcinfo/0.2.0

The #crate now allows to write #SRCINFO data to file, has seen improvements to the interface and documentation as well as a few bug fixes.

For further details refer to the #changelog https://alpm.archlinux.page/alpm-srcinfo/CHANGELOG.html#020---2025-06-16

The new alpm-package #crate offers integration with #ALPM based #package files.

https://crates.io/crates/alpm-package/0.1.0

Currently it allows to create package files from prepared input directories and supports the #bzip2 #gzip #xz and #zstd #compression algorithms.

The alpm-pkginfo #crate in version 0.2.0 offers an easier interface for creating package info data from #PKGINFO files.

https://crates.io/crates/alpm-pkginfo/0.2.0

This #library and #CLI crate offers integration with the #PKGINFO #metadata files found in #ALPM based #package files.

See the #changelog for details: https://alpm.archlinux.page/alpm-pkginfo/CHANGELOG.html#020---2025-06-16

With version 0.2.0 the #library and #CLI alpm-mtree offers new features that allow validating a directory with #MTREE data, as well as creating #MTREE data from a directory.
Additionally, we have improved the usability of the parser and the documentation.

The #crate provides integration with the #ALPMMTREE file format which is used in #ALPM based #package files.

https://crates.io/crates/alpm-mtree/0.2.0

For details refer to the #changelog https://alpm.archlinux.page/alpm-mtree/CHANGELOG.html#020---2025-06-16

The #library and #CLI alpm-buildinfo in version 0.2.0 offers many documentation and usability improvements for this #crate providing integration with the #BUILDINFO file format which is used in #ALPM based #package files.

https://crates.io/crates/alpm-buildinfo/0.2.0

For details refer to the #changelog https://alpm.archlinux.page/alpm-buildinfo/CHANGELOG.html#020---2025-06-16

@governa kool, I hope it will also be distributed as #flatpak #package. It would have the same limitations as flatpak version of #gnomeboxes but for the most basic usage of spinning up #virtualmachine without any special network interfaces or other stuff that requires privilaged user intervention.

@unix_discussions Why they compared tge size of the executable file, with the size of #flatpak package? Shouldnt we at least try to include for standard #linux #package all #dependencies it requires or at lest compare #staticlinking with their flatpak counterparts to get rough estimate of flatpak metadata size overhead, and dependency duplication from runtime and separately whatever was put alongside the contenerized application. Also, it would be cool to compare it across many #linuxdistribution in case there are some that due to #dynamiclinking have to bundle multiple versions of given library

The European Commission released its "AI Continent Action Plan" last week. This high-level communication lays down the various initiatives the European Commission is pursuing to support Europe's AI ambitions and AI uptake: https://iapp.org/news/a/a-view-from-brussels-what-is-and-isn-t-in-the-eu-s-ai-continent-action-plan

@peppe Actually, (almost) every #FreeBSD #port should also be available as a binary #package. When one is missing, this typically indicates a build failure on the latest bulk run. Trying to build it yourself won't help here unless there was a fix committed to the ports tree meanwhile, in which case the package will also "reappear" within few days.