Arch Linux User Repository

Ah, I see! I've filed a merge request.

You're totally right! There is no difference now. I didn't notice that the next branch has been merged into main.

This means this package can probably be removed at this point, as it's no longer needed.

Is there any difference between this and https://aur.archlinux.org/packages/fractal-git?

Alright, it's a runtime dependency. Fractal won't launch without it.

Looks like there's a missing dependency. Not sure if it's just build-time or runtime. libshumate

The following warnings were emitted during compilation:

warning: `"pkg-config" "--libs" "--cflags" "shumate-1.0" "shumate-1.0 >= 0"` did not exit successfully: exit status: 1

error: failed to run custom build command for `libshumate-sys v0.1.0-alpha.4`

Caused by:
  process didn't exit successfully: `/home/satcom886/.cache/yay/fractal-next/src/fractal/_build/src/release/build/libshumate-sys-277873c8bf2da054/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=SHUMATE_1.0_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:warning=`"pkg-config" "--libs" "--cflags" "shumate-1.0" "shumate-1.0 >= 0"` did not exit successfully: exit status: 1
  error: could not find system library 'shumate-1.0' required by the 'libshumate-sys' crate

  --- stderr
  Package shumate-1.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `shumate-1.0.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'shumate-1.0', required by 'virtual:world', not found
  Package 'shumate-1.0', required by 'virtual:world', not found

warning: build failed, waiting for other jobs to finish...
error: build failed
[38/39] Generating data/org.gnome.Fractal.metainfo.xml with a custom command
FAILED: src/fractal 
/usr/bin/env CARGO_HOME=/home/satcom886/.cache/yay/fractal-next/src/fractal/_build/cargo-home /usr/bin/cargo build --manifest-path /home/satcom886/.cache/yay/fractal-next/src/fractal/Cargo.toml --target-dir /home/satcom886/.cache/yay/fractal-next/src/fractal/_build/src --release && cp src/release/fractal src/fractal
ninja: build stopped: subcommand failed.

Thanks for the heads-up, q234rty. I updated the PKGBUILD to follow the main branch and modified the pkgver() to reflect the upstream name "5.alpha".

This fails to build as upstream has switched to the main branch. Also versioning probably needs to be reworked as well.

there is fractal-next here: https://aur.archlinux.org/packages/fractal-next/ .

@szbergeron I tried building this with libadwaita and gtk4 from extra, but it fails with Dependency libadwaita-1 found: NO found 1.0.0 but need: '>= 1.0.0-alpha.1'

Probably upstream needs to catch up.

EDIT: Anyway, it fails with libadwaita-git as well. I pushed the changes you mentioned.

EDIT2: I added a sed command in prepare() to fix the broken meson.build file. I compiled locally and works.

gtk 4.6 is now in extra and next appears to work on top of it. Maybe we can update this to dep on gtk4 instead of strictly gtk4-git?