Search Criteria
Package Details: mqtt-explorer 0.3.5-13
Package Actions
Git Clone URL: | https://aur.archlinux.org/mqtt-explorer.git (read-only, click to copy) |
---|---|
Package Base: | mqtt-explorer |
Description: | A comprehensive and easy-to-use MQTT Client |
Upstream URL: | https://mqtt-explorer.com/ |
Licenses: | CCPL:by-nd |
Conflicts: | mqtt-explorer-beta |
Submitter: | dave12311 |
Maintainer: | zhimsel (aarnold) |
Last Packager: | zhimsel |
Votes: | 11 |
Popularity: | 0.000004 |
First Submitted: | 2020-02-23 16:05 (UTC) |
Last Updated: | 2023-03-17 14:55 (UTC) |
Dependencies (5)
- nodejs (nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron, nodejs-lts-jod)
- git (git-gitAUR, git-glAUR) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- sed (busybox-coreutilsAUR, sed-gitAUR) (make)
- yarn (yarn-pnpm-corepackAUR, yarn-berryAUR, corepackerAUR) (make)
Latest Comments
1 2 3 4 5 Next › Last »
zhimsel commented on 2025-01-12 15:54 (UTC)
@mqs Ah, that's interesting. I just looked into the built package, and sure enough, it's ~1GiB. It's all the NodeJS module dependencies (i.e.
node_modules
). However, those appear to be (at least in part) required to run the program. I'm sure they can be thinned down after build, but I don't know enough about the upstream program (and what is required and what is not) to confidently strip things out. If you want to save space, the appimage is your best bet, most likely.If you're able to thin out this package safely, I'd happily accept contributions to the package. If you do, shoot me an email and we can work out getting any patches applied.
mqs commented on 2025-01-11 22:09 (UTC)
I just now tried to switch from the -appimage package to this one (wanted to build this from source myself) and saw that this increased the size of the installed files from ~70MB (the -appimage package) to 1GB (this package). Is there a reason for this?
Maaike commented on 2024-07-31 09:45 (UTC)
Bit late response but that helped, thank you!
zhimsel commented on 2024-06-08 15:57 (UTC)
@Maaike it looks like this is a bug in the Linux kernel. Supposedly, it should be fixed in 6.9.3:
In the meantime, you can work around this by setting the
UV_USE_IO_URING=0
environment variable when building the package (i.e.UV_USE_IO_URING=0 makepkg -s
).Maaike commented on 2024-06-04 16:21 (UTC)
Installing does not work:
sshine commented on 2023-06-06 11:39 (UTC) (edited on 2023-06-06 11:58 (UTC) by sshine)
Upon
makepkg -si
,It seems that we want to add
typescript
as a dependency.aarnold commented on 2023-05-22 15:02 (UTC) (edited on 2023-05-22 15:05 (UTC) by aarnold)
@turiok you might try to contact the packager:
turiok commented on 2023-05-22 10:18 (UTC)
I have the same problem with bitwarden. I think the best solution is to change bitwarden. Because they use nodejs only for the build. And to solution that, I found this article https://wiki.archlinux.org/title/Node.js_package_guidelines#Using_nvm But I don't know how to ask this because bitwarden is an official package
jhf2442 commented on 2023-04-04 21:46 (UTC)
@zhimsel yes, the problem is that ndejs-lts-gallium provides a version too old for this package, thus the conflict. Else I would have tried modifying the PKGBUILD, but from your comment of 2023-03-15, I deduced that it's not worth it
Nevertheless good hint with the appimage - will go for the mqtt-explorer-appimage package to prevent the version collision. Many thanks !
zhimsel commented on 2023-04-04 13:56 (UTC) (edited on 2023-04-04 13:57 (UTC) by zhimsel)
Actually, this could be solved (potentially) by the
nodejs-lts-gallium
package providingnodejs
via its PKGBUILD. Then it would satisfy the dependency.EDIT: It does: https://github.com/archlinux/svntogit-community/blob/ec35ab863ae7f597a1225d331fe4767de21a607a/trunk/PKGBUILD#L15. Just not the right version (for us).
1 2 3 4 5 Next › Last »