Search Criteria
Package Details: bauh-staging 0.10.8.RC-2
Package Actions
| 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: | 7 |
| Popularity: | 0.005121 |
| First Submitted: | 2019-08-12 16:09 (UTC) |
| Last Updated: | 2024-05-25 11:52 (UTC) |
Dependencies (41)
- python (python37AUR, python311AUR, python310AUR)
- python-colorama (python-colorama-gitAUR)
- python-dateutil
- python-pyaml
- python-pyqt5 (python-pyqt5-sip4AUR, python-pyqt5-webkitAUR)
- python-pyqt5-sip
- python-requests
- qt5-svg (qt5-svg-gitAUR)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-wheel (make)
- aria2 (aria2-gitAUR, aria2-proAUR, aria2-fastAUR, aria2-unlimitedAUR) (optional) – multi-threaded downloading support
- autoconf (autoconf-gitAUR) (optional) – may be required to compile some AUR packages
- automake (automake-gitAUR) (optional) – may be required to compile some AUR packages
- axel (optional) – multi-threaded downloading support
- binutils (optional) – required for AUR support
- bison (byacc-bisonAUR, bison-gitAUR) (optional) – may be required to compile some AUR packages
- breeze (breeze-gitAUR) (optional) – KDE Plasma main theme
- ccache (ccache-gitAUR) (optional) – can improve AUR packages compilation speed
- fakeroot (fakeroot-gitAUR, fakeroot-tcpAUR) (optional) – may be required to compile some AUR packages
- flatpak (flatpak-gitAUR) (optional) – required for Flatpak support
- flex (flex-gitAUR) (optional) – may be required to compile some AUR packages
- fuse2 (optional) – may be required for AppImage support
- fuse3 (fuse3-gitAUR) (optional) – may be required for AppImage support
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc11AUR, gcc-snapshotAUR) (optional) – may be required to compile some AUR packages
- git (git-gitAUR, git-glAUR) (optional) – required for AUR support
- lib32-fakeroot (optional) – may be required to compile some AUR packages
- m4 (m4-gitAUR) (optional) – may be required to compile some AUR packages
- make (make-gitAUR) (optional) – may be required to compile some AUR packages
- pacman (pacman-gitAUR) (optional) – required for AUR support
- patch (patch-gitAUR) (optional) – may be required to compile some AUR packages
- pkgconf (pkgconf-gitAUR) (optional) – may be required to compile some AUR packages
- python-beautifulsoup4 (optional) – for Native Web applications support
- python-lxml (optional) – for Native Web applications support
- rebuild-detector (optional) – enables rebuild checking for AUR packages (optional)
- shadow (shadow-selinuxAUR) (optional) – to install AUR packages as the root user
- snapdAUR (snapd-gitAUR) (optional) – required for Snap support
- sqlite3 (sqlite) (optional) – required for AppImage support
- util-linux (busybox-coreutilsAUR, util-linux-selinuxAUR, util-linux-aesAUR) (optional) – to install AUR packages as the root user
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR) (optional) – to open URLs in the browser
Latest Comments
Locutus64 commented on 2023-11-21 13:06 (UTC)
Bauh-Staging will not install. I had 4 other AUR apps that were installed without issue. Any thoughts?
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:To fix and update to release v0.10.1, you need to declare:
Next time I suggest you omit the
'.'before the'RC'suffix, and declare something like: