What makes your Rolling Release stable?

buhtz · 2022-08-24 17:56:42

This is nearly an X-Post from the Manjaro "Forum", but not exactly: https://forum.manjaro.org/t/what-makes- … ble/120277

I’m a becoming(!) upstream maintainer of a Python application. I use Debian and don’t know much about other distributions. But as a upstream maintainer I have to learn some things. That is why I am asking. :slight_smile: I don’t want to troll or start heavy and hot pro and cons discussions.

The question is why your rolling release model makes a stable distribution?
I assume it is stable. In another case you wouldn’t have so much users.

I know rolling release from Debians unstable and testing branches which are special cases and they are not stable by default and not for productive use.

What mechanisms you have to be (nearly) sure that your releases are stable? Is there a quality check or something?

I can't find "my" application "backintime" in your package repo. I will work on it.
So let's see python3-green as another example.

I found that [tt]PKGBUILD[/tt] file in your repo.

It seems to me that you install direct from the upstream GitHub repo, right?
Which version/tag/commit do you use here? I can’t understand that in the script.

Am I right so far with my journey?

ewaller · 2022-08-24 18:09:28

ewaller@odin/home/ewaller/devel/python % auracle search backintime
aur/backintime 1.3.2-2 (285, 1.322)
    Simple backup system inspired from the Flyback Project and TimeVault. QT5 GUI version.
aur/backintime-cli 1.3.2-2 (285, 1.322)
    Simple backup system inspired from the Flyback Project and TimeVault. CLI version.
aur/backintime-cli-git 1.3.1.r1.ge1ae23dd-2 (27, 0.016157)
    Simple backup/snapshot system inspired by Flyback and TimeVault. CLI version.
aur/backintime-git 1.3.1.r1.ge1ae23dd-2 (27, 0.016157)
    Simple backup/snapshot system inspired by Flyback and TimeVault. Qt5 GUI version.
ewaller@odin/home/ewaller/devel/python %

auracle is a an unoffical tool for handling things in what we call the AUR (Arch user repository)
https://wiki.archlinux.org/title/Arch_User_Repository. The AUR is a place where there are build instructions for packages that are not in our official repositories. We have a group of "Trusted Users" who are developers and packagers who have rights to promote things from the AUR into the "Community" repository. Official Arch developers maintain the core and Extra repositories (as well as test). Your program seems to have several options available in the AUR.

We tend to install Python packages for all users and try to have all Python programs in the repositories use those versions (generally the latest). You will need to read https://wiki.archlinux.org/title/Python … guidelines

Welcome, and thank you.

Edit: Other resources:
https://wiki.archlinux.org/title/PKGBUILD
https://wiki.archlinux.org/title/Makepkg
https://wiki.archlinux.org/title/Arch_Build_System
https://wiki.archlinux.org/title/Pacman

Last edited by ewaller (2022-08-24 18:14:26)

Trilby · 2022-08-24 18:35:35

buhtz wrote:

So let's see python3-green as another example.
I found that [tt]PKGBUILD[/tt] file in your repo.
It seems to me that you install direct from the upstream GitHub repo, right?
Which version/tag/commit do you use here? I can’t understand that in the script.

The source for that package is downloaded from github, but not from the VCS code, rather an archived tarball of version 3.4.1. You can see the source array referrs to the url for the source which uses variables including pkgver which are defined just a few lines above.

walkingstickfan · 2022-08-25 05:36:42

Knowing how to use it and knowing how to resolve the inevitable issue that may crop up from time to time.

Arch Linux

#1 2022-08-24 17:56:42

What makes your Rolling Release stable?

#2 2022-08-24 18:09:28

Re: What makes your Rolling Release stable?

#3 2022-08-24 18:35:35

Re: What makes your Rolling Release stable?

#4 2022-08-25 05:36:42

Re: What makes your Rolling Release stable?

Board footer