Search Criteria
Package Details: spectroterm 0.5.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/spectroterm.git (read-only, click to copy) |
---|---|
Package Base: | spectroterm |
Description: | Curses based terminal spectrum analyzer for currently playing audio |
Upstream URL: | https://github.com/mzivic7/spectroterm |
Keywords: | spectrum-analyzer tui |
Licenses: | GPL-3.0-only |
Submitter: | mzivic |
Maintainer: | mzivic |
Last Packager: | mzivic |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2025-05-23 19:30 (UTC) |
Last Updated: | 2025-07-22 18:00 (UTC) |
Latest Comments
mzivic commented on 2025-07-22 18:03 (UTC)
Thanks, I fixed almost all from your suggestions. There are no missing dependencies,
spectroterm
is standalone binary executable built with nuitka inonefile
mode, which means it needs no python nor any modules. Butspectroterm-git
builds it with pyinstaller (because nuitka takes a long time to compile), and all the dependencies are still only at build-time.I don't like making it into wheel because I'm using nuitka, which converts all python code to C, then compiles it, optionally with clang, collects dlls, and finally combines it all into one executable. This gives better performance than using python interpreted code. And here performance really is important. The only purpose I have pyproject.toml is so it can hold list of dependencies for uv. And setup.py is for cython extensions compilation.
envolution commented on 2025-07-20 21:08 (UTC) (edited on 2025-07-20 21:27 (UTC) by envolution)
Just a few suggestions mzivic:
missing dependencies (ie. python, and modules you list in pyproject.toml) -
license
should match a spdx string included in licenses (if it matches) or you should provide the appropriate license file:While your -git package should provide and conflict with
spectroterm
this package should not as it's already implied by the$pkgname
Since you're the author and already have a pyproject.toml and setup.py, you may consider building a wheel and installing it as described in the guide at: https://wiki.archlinux.org/title/Python_package_guidelines - you can review examples on aur from
python-ultralytics
oraurdex
for referencesalso when sourcing with an aliased name like $pkgname.tar.gz you can run into cached file conflicts - it's better to use $pkgname-$pkgver.tar.gz in this case