Okay, next big thing: get `svt-av1-psyex` packaged up for installation on Arch Linux. Figured the easiest way would be to grab the PKGBUILD for `svt-av1-psy-git` and tweak as necessary. Also, need to add Dolby Vision and HDR10+ support because reasons.
О пакетах в экосистеме Apple (часть 2)
Всем привет! Это снова Эрик, инженер технической поддержки из Ринго , и мы продолжаем разговор о пакетах в экосистеме Apple. В первой части мы разобрали теорию : изучили устройство PKG-файлов, познакомились с Gatekeeper и нотаризацией, научились инспектировать пакеты с помощью встроенных утилит. Теперь перейдём к практике — будем создавать и переупаковывать пакеты.
https://habr.com/ru/companies/ringo_mdm/articles/960864/
#pkg #pkgbuild #macos #установочные_пакеты #MDM #productbuild #переупаковка_приложений #создание_PKG_из_DMG #distributive_package #развёртывание_ПО
Un aperçu de la gestion de paquets pour AUR via WSL 2 sous MS-Windows 11
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
Was recently configuring two servers (#almalinux and #ubuntu) and found that some packages would require to use their "community" packages, with some features not fully implemented.
I miss the quick, clean and easy way of defining install instructions of #pkgbuild of #archlinux
I ended up transforming ArchLinux #aur packages to scripts, and running them on both servers 😅
Is there a tool that can read an AUR package and "just install" it on a server, not Arch based?
BassBoom is now easier to install!
We have made some of the biggest changes in BassBoom. This time, it’s about packaging the software for easier installation. Starting from BassBoom 0.1.12 and 0.2.7, we are providing the following package installers for different systems:
As we’ve promised, we’ve made installation of the BassBoom application easier than never before by shipping different types of installers apart from the regular distribution method that utilizes the packaged ZIP file for the application itself.
The documentation will be updated soon to provide instructions on how to install BassBoom using one of the above packaging methods that we’ve recently introduced. This will make your experience regarding installation of BassBoom smoother than before and save your time extracting the archive and remembering the path to the executable file.
If you’ve used the Windows Installer to install BassBoom, you’ll be greeted with this screen:
Just follow the instructions on the screen, and you’re done!
As for the Launchpad PPA, we’re uploading the packages that correspond to the API version of BassBoom releases to the archive. To install BassBoom, use the following commands:
$ sudo add-apt-repository ppa:eofla/bassboom$ sudo apt update$ sudo apt install bassboomThen, follow the instructions on the screen to select a version series to install, currently being:
As for the Arch Linux distribution, use your AUR helper to install one of the following packages, depending on what series you want to install:
You can download BassBoom 0.1.13 and 0.2.8 here:
Download 0.2.8 Download 0.1.13#arch #ArchLinux #bassboom #deb #dpkg #Launchpad #LaunchpadPPA #news #PKGBUILD #Tech #Technology #Ubuntu #update #Windows #WindowsInstaller
This is the Ubuntu PPA for our software, BassBoom, which can be found here: https://github.com/Aptivi/BassBoom. BassBoom aims to be a project that is a cross-platform music player written in C# and .NET, with libmpg123 as a native library backend for 0.1.x and 0.1.2 and libmpv as a native library for 1.0.0 and higher. WARNING: Only compatible with Ubuntu 24.04 Noble Numbat or later! If you're running older Ubuntu versions, download the release zip files found in the GitHub project. This is ...
Sorry to all early adopters for the confusion with my very strict and hard cut #Luanti 
package for #Arch 
in the #AUR (see here for the pkgbase).
But I think it’s all settled now and the naming convention is matched and the compiling options are okay and the #PKGBUILD is free from errors (famous last words 🙃)
So if you’re an Arch Linux user and want a “clean” and most recent release version Luanti package, maybe try mine. It tries the best to get rid of the old name and exclusively use “Luanti”.
As a “normal end-user” not hosting a server and not caring too much about having development documentation available offline, you just need two of the four split packages (luanti-modern-client and luanti-modern-common) to run a Luanti client.
The shared directories, etc. are all adapted, the only thing that currently seems not to be changeable are the user-specific directories/files like ~/.minetest or ~/.minetest/minetest.conf (I wasn’t able to find a compiling option changing this.)
By default, #SDL2 is enabled, so the client runs natively on #Wayland 
setups. Just check the PKGBUILD before creating the packages, there is an option for that to change this.
Jason Weatherly
Patrick 
Habr
Salvatore Noschese 🇮🇹
Tonton Fred
David Runge
Emanuele Panz
Aptivi
Hunter Jozwiak
𝘋𝘪𝘳𝘬