Recent searches

No recent searches

Search options

Only available when logged in.
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

fosstodon.org: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#PKGBUILD

0 posts0 participants0 posts today
Continued thread
David Runge

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. 📦 🦀 📄

crates.io/crates/alpm-srcinfo/

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 alpm.archlinux.page/alpm-srcin

crates.iocrates.io: Rust Package Registry
#ArchLinux#PKGBUILD#RustLang
Emanuele Panz

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?

#fedihelp#sysadminlife
*
Aptivi

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:

  • Windows Installer for Windows systems
  • Launchpad PPA for Ubuntu
  • PKGBUILD for Arch Linux using the AUR

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 bassboom

Then, follow the instructions on the screen to select a version series to install, currently being:

  • bassboom-1: Installs BassBoom v0.1.x series
  • bassboom-2: Installs BassBoom v0.2.x series

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:

  • bassboom-1: Installs BassBoom v0.1.x series from the latest release tag
  • bassboom-1-git: Installs BassBoom v0.1.x series from the live servicing branch
  • bassboom-2: Installs BassBoom v0.2.x series from the latest release tag
  • bassboom-2-git: Installs BassBoom v0.2.x series from the live servicing branch
  • bassboom-3-git: Installs an upcoming version of BassBoom from the live servicing branch

You can download BassBoom 0.1.13 and 0.2.8 here:

Download 0.2.8 Download 0.1.13

Image by freepik

#arch#ArchLinux#bassboom
𝘋𝘪𝘳𝘬

Sorry to all early adopters for the confusion with my very strict and hard cut #Luanti :luanti: package for #Arch :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 :wayland: setups. Just check the PKGBUILD before creating the packages, there is an option for that to change this.

aur.archlinux.orgAUR (en) - luanti-modern
*
🅴🆁🆄🅰 🇷🇺
Про пакеты в #AUR у дистрибутива #ArchLinux #Manjaro #EndeavourOS.
Чтобы не утягивался весь #git -репозиторий логично использовать «--depth 1» и приходится это указывать у каждого пакета в #PKGBUILD:
...
prepare() {
  ...
  git clone --depth 1 https://...
  cd $pkgname
  git submodule update --init --recursive --depth 1
  ...
}
Т. е. воз и ныне там, без шансов, что ситуация изменится в обозримом будущем — на более высоком уровне работу с git'ом не поправить, чтобы махом и для всех

Как вариант может быть и такое:
...
prepare() {
  ...
  git clone --recurse-submodules --depth=1 https://...
  ...
}

Вот только использование конструкции:
  git clone --recurse-submodules --depth=1 https://...
не приводит к тому, чтобы и сабмодули с «--depth 1» выкачивались.
А этих самых submodules может быть много и сами при этом довольно объёмные.

#linux #lang_ru
hub.hubzilla.deHubzilla.de
#lang_ru
TrendingLive feeds
About