Package Details: bauh-staging 0.10.3.RC-10

Git Clone URL: https://aur.archlinux.org/bauh-staging.git (read-only, click to copy)
Package Base: bauh-staging
Description: Graphical interface for managing your applications (AppImage, Flatpak, Snap, Arch/AUR, Web). Testing branch (it may not be working properly).
Upstream URL: https://github.com/vinifmor/bauh
Licenses: zlib/libpng
Conflicts: bauh
Provides: bauh
Submitter: vfm90
Maintainer: vfm90
Last Packager: vfm90
Votes: 4
Popularity: 0.041608
First Submitted: 2019-08-12 16:09 (UTC)
Last Updated: 2022-05-27 18:18 (UTC)

Latest Comments

MarsSeed commented on 2022-04-08 18:34 (UTC)

Now I see the new commits on the staging branch. Thanks for clarifying your branch packaging strategy.

Anyway this is a nice and very useful application. Keep up the good work! :)

vfm90 commented on 2022-04-04 15:19 (UTC)

@MarsSeed, staging is a different branch from master. You can have a look on the project's GitHub page. Not all content published on the staging branch is merged into the master branch.

About the versions: 0.10.1-1 is greater than 0.10.1.RC-4. You can try the following code using the Python's interpreter:

from packaging.version import LegacyVersion

v1 = LegacyVersion('0.10.1-1') v2 = LegacyVersion('0.10.1.RC-4') print(v1 > v2)

Generally the latest stable release is equivalent to the latest RC release (staging), because some breaking or not ready features are removed.

bauh follows the same principles of wine and wine-staging. You just can have one of them installed on your system.

MarsSeed commented on 2022-04-01 13:05 (UTC) (edited on 2022-04-08 18:28 (UTC) by MarsSeed)

@vfm90 it's fine that this package is for development releases.

But currently this is not from a different path, it's from the master branch.

Only it is 2 commits behind release v0.10.1.

It is therefore missing these fixes.

So why punish willing 'beta-testers' by not letting them have the latest version and keep them stuck on an earlier unfixed version?

If you want to have a truly separate development or staging path for this application, please kindly consider changing the packaging as to let users install bauh and bauh-staging side-by-side without conflicts, à la firefox & firefox-developer-edition.

vfm90 commented on 2022-04-01 12:32 (UTC)

bauh-staging follows a different versioning path from the stable release. Here comes testing features and behaviors that might not be available on the stable release. It should be treated as a separate package.

MarsSeed commented on 2022-04-01 10:20 (UTC) (edited on 2022-04-01 10:24 (UTC) by MarsSeed)

Please be aware that for Pacman, the current '.RC-4' suffixed version is newer than the final release version v0.10.1:

0.10.1RC-4 < 0.10.1 < 0.10.1.RC-4

To fix and update to release v0.10.1, you need to declare:

epoch=1
pkgver=0.10.1

Next time I suggest you omit the '.' before the 'RC' suffix, and declare something like:

pkgver=0.11.0RC
## or more preferably:
pkgver=0.11.0rc