Arch Linux User Repository

@jhf2442 sorry for the delayed response. I'm not really sure what the best practice is for this. Within any package management system, there's always the chance for conflicting dependencies; Pacman is not immune to this (especially in the AUR). Given that the build requires nodejs>=17, I'm not sure really how to address this.

Maybe you could create a package out of the AppImage (which are released in the Github repo). Or you could fork this package to work with a lower version of nodejs.

@jhf2442 I guess it's possible to adapt the build script to use different arguments/patches for different nodejs versions. But I'm not sure if this is the best solution in the context of a rolling release distribution as well within the yarn/npm/nodejs ecosystem. Maybe somebody can share his/her knowledge.

Unfortunately, requiring nodejs>=17 now introduces a conflict with bitwarden-cli from community repo !

looking for conflicting packages...
:: nodejs and nodejs-lts-gallium are in conflict. Remove nodejs-lts-gallium? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nodejs-lts-gallium breaks dependency 'nodejs-lts-gallium' required by bitwarden-cli
 -> error installing repo packages

How can we solve this ?

@StefanK2 I updated the PKGBUILD to require v17 or higher. That should hopefully avoid anyone else having issues in the future.

@aarnold yes, that was it. For some reason I had a node v14 lts version installed. I switched the package and now it builds correctly.

Thank you very much :)

@StefanK2: I think this argument became necessary with nodeJS v17 and above. Which version do you use? (node -v)

Currently building results in this error for me:

==> Starting build()...
node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
==> ERROR: A failure occurred in build().
    Aborting...

Removing this line from PKGBUILD seems to resolve it, the build works:

export NODE_OPTIONS=--openssl-legacy-provider

@BrainDamage: doh! You are absolutely correct. That is what I do in my other packages, I don't know why I ended up doing it this way here. Thanks for the heads up. Just pushed the fix.

install -Dm 0644 "${srcdir}/../mqtt-explorer.desktop" "${pkgdir}/usr/share/applications/mqtt-explorer.desktop"
install -Dm 0755 "${srcdir}/../mqtt-explorer-run.sh" "${pkgdir}/usr/bin/mqtt-explorer"

this method of sourcing is incorrect, it assumes that ${BUILDDIR} and ${SRCDEST} are mutually nested, while that's what happens by default, that's not always the case because the user can change their values through environment variable (see makepkg man page for their infos)

as a quick test you can try:

BUILDDIR=$(mktemp -d) makepkg

and this pkgbuild will fail (or any other non-default BUILDDIR path)

the correct way to source them is to append the .desktop and .run file to the source array, simply by passing their name like this:

source=(
    "$pkgname-${pkgver}.tar.gz::https://github.com/thomasnordquist/MQTT-Explorer/archive/v$pkgver.tar.gz"
    'mqtt-explorer.desktop'
    'mqtt-explorer-run.sh'
    )

this will make makepkg copy the files into ${BUILDDIR} so you can source them as:

install -Dm 0644 "${srcdir}/mqtt-explorer.desktop" "${pkgdir}/usr/share/applications/mqtt-explorer.desktop"
install -Dm 0755 "${srcdir}/mqtt-explorer-run.sh" "${pkgdir}/usr/bin/mqtt-explorer"

(yes, ${BUILDDIR} gets translated to ${srcdir} inside makepkg because the files are extracted/copied there, it's a bit confusing)

This should build properly now (v 0.3.5-8).