Package Details: dosbox-staging 1:0.82.2-1

Git Clone URL: https://aur.archlinux.org/dosbox-staging.git (read-only, click to copy)
Package Base: dosbox-staging
Description: DOS/x86 emulator focusing on ease of use. Based on DOSBox
Upstream URL: https://github.com/dosbox-staging/dosbox-staging
Keywords: dos emulator games gaming
Licenses: GPL-2.0-or-later
Conflicts: dosbox
Provides: dosbox
Submitter: sharkwouter
Maintainer: silverhikari
Last Packager: silverhikari
Votes: 52
Popularity: 0.057887
First Submitted: 2020-03-14 13:37 (UTC)
Last Updated: 2025-06-22 00:07 (UTC)

Required by (58)

Sources (1)

Latest Comments

1 2 3 4 5 Next › Last »

silverhikari commented on 2025-06-03 07:01 (UTC)

@Toumal thanks for the heads up

Toumal commented on 2025-05-31 10:21 (UTC)

@silverhikari FYI dosbox-staging is moving from meson to cmake for the build process, so the next release won't build with meson anymore. There's currently no "install" target for cmake, but that should be done soon.

hfc2x commented on 2025-05-08 23:53 (UTC)

@silverhikari dosbox-staging-bin works as far as keyboard keys is concerned, but introduces a plethora of other packaging-related issues that makes it very much not ideal to use.

silverhikari commented on 2025-04-24 21:11 (UTC) (edited on 2025-04-24 21:11 (UTC) by silverhikari)

@hfc2x if using a aur-helper you can alter the munt pkgbuild to add "-DCMAKE_POLICY_VERSION_MINIMUM=3.5" after "-Dmunt_WITH_MT32EMU_SMF2WAV=ON" though remember to add the "\" before adding it, this issue is caused by the recent update to cmake 4.0 so not all packages have been updated to fix it. for the other issue can you test dosbox-staging-bin to see if this is still a problem as that package uses the precompiled upstream release

hfc2x commented on 2025-04-21 01:50 (UTC) (edited on 2025-04-21 19:52 (UTC) by hfc2x)

This does not work anymore because the Munt version in the AUR spits out an error when compiling, causing dosbox-staging to fail to build as well.

This build also introduces this bug. The bug is not found in the official precompiled binaries, which meant the developers flagged this problem as "not a bug" on their end.

harmathy commented on 2024-03-11 17:40 (UTC) (edited on 2024-03-11 17:41 (UTC) by harmathy)

@harmathy the tarball(if it is this one "dosbox-staging-linux-v0.81.0.tar.xz") is a binary release not a source release, this package is to build it from source. if you want a binary release use the package dosbox-staging-bin

@silverhikari ah, sorry. I somehow missed that.

Another possibility is to use the git repository and the release tag.

source=("git+https://github.com/dosbox-staging/${pkgname}#tag=v${pkgver}")
sha256sums=('SKIP')

A lot of other AUR packages use this pattern.

silverhikari commented on 2024-03-11 16:21 (UTC)

just test the checksum again and it seems to be working, you may need to delete the src/ folder and the v0.81.0.tar.gz

silverhikari commented on 2024-03-11 16:14 (UTC)

@harmathy the tarball(if it is this one "dosbox-staging-linux-v0.81.0.tar.xz") is a binary release not a source release, this package is to build it from source. if you want a binary release use the package dosbox-staging-bin

harmathy commented on 2024-03-11 15:57 (UTC) (edited on 2024-03-11 15:57 (UTC) by harmathy)

This PKGBUILD uses the github generated tarball which may change checksum anytime. Use the tarball provided by upstream!

source=("https://github.com/dosbox-staging/${pkgname}/releases/download/v${pkgver}/${pkgname}-linux-v${pkgver}.tar.xz")
sha256sums=('034b08a941a7fd0279a81b10af620999c569f7e81b786e7f4b59a0b94e46d399')

kIERO commented on 2024-03-11 15:10 (UTC) (edited on 2024-03-11 15:11 (UTC) by kIERO)

This build is still broken because of the sha256sum

1 2 3 4 5 Next › Last »