Arch Linux User Repository

Just a heads up, aml got bumped to v1.0, extra/aml still has to catch up (it's on v0.3.0). Compilation fails with it (duh).

Not sure what's the cleanest solution for compiling right-now. aml-git exists, but that could maybe break anyone who uses extra/neatvnc and extra/wayvnc. Then there's aml1, but that requires updating the PKGBUILD (plus that AUR package will become very redundant as soon as extra/aml catches up).

@gaku999 aml v1.0 is coming soon to the extra repo. https://gitlab.archlinux.org/archlinux/packaging/packages/aml

Just a heads up, aml got bumped to v1.0, extra/aml still has to catch up (it's on v0.3.0). Compilation fails with it (duh).

Not sure what's the cleanest solution for compiling right-now. aml-git exists, but that could maybe break anyone who uses extra/neatvnc and extra/wayvnc. Then there's aml1, but that requires updating the PKGBUILD (plus that AUR package will become very redundant as soon as extra/aml catches up).

Doesn't build in chroot for me - complains about a missing libdrm and then gbm.

EDIT: had to add libdrm, mesa and ffmpeg to MAKEDEPENDS.

@ruahcra now it builds fin with libvncserver from extra as well!

@ruahcra wlvncc builds and runs fine for me with package aml from community, aml-git is not needed. If you change the dependency to aml, we can have the wayvnc package from community installed at the same time!

@tinywrkb Sorry about that, I actually have no memory of this... guess I was rushing things at the time and didn't pay enough attention. Anyway I added you as a co-maintainer if you'd like to help out, otherwise I will look into it sometime in the future.

@ruahcra thanks for submitting the package, I've been avoiding doing so myself, so it's great that someone else maintaining it.
There are a few issues though with the packaging. Going from top to bottom, not in severity order:

• arch array: are you really testing all these architectures? If not, then please don't add untested arch, this means that the packaging officially supports this archs, but in reality you don't. I guess you can put this issue under the category false advertising. The makepkg --ignorearch flag exist for a reason.
• makedepends array: you have here unneeded packages. ninja is a dependency of meson. pkg-config or more correctly pkgconf, is already included in the base-devel group that expected to be installed (should not be added to makedepends, see the PKGBUILD Arch Wiki page).
• provides array: wlvncc does not provide a shared lib, so there's no point in setting a provided version. Also, it's pretty much wrong to set the lib version like this, it should match the shared lib version, not the package version.
• pkgver function: you should prepare the version for a tagged release, see the VCS package guidelines Arch Wiki page. Maybe something like this:

( set -o pipefail
    git describe --long --tags 2>/dev/null | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g' ||
    printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
  )

• build function: you're not following the Meson package guidelines.

arch-meson wlvncc build
meson compile -C build

• package function: same as the previous.

meson install -C build --destdir "$pkgdir"