No Linters Available
No Unit Test Coverage
This package does not appear to have been generated using our generating a package.yml script per this documentation, the spacing is completely off.
Your builddeps need to be ordered by pkgconfigs first, followed by alphabetical static deps. Additionally you have some unnecessary builddeps listed, please check the reverse dependencies to make sure you're not listing stuff that will get pulled in by being a dependency.
Should be cleaned up, you're listing a bunch of deps that will get automatically pulled in or are being linked against.
You should be using our actionable macro for this.
I think it's a good start however there's still some cleanup, alphabetizing of explicit rundeps (making sure any that are in the abi_used_libs, which means are being linked and thus already picked up as dependencies) aren't listed, etc. Also, do we really need both Qt5 and GTK3 support or can it be one or the other?
You may want to re-evaluate your runtime dependencies and make sure the python ones you're listing are all actually needed. Also, does it actually need all those python dependencies as build deps (necessary only if it's checked for in configuration time, used for building or test suites) or are they just rundeps?
Good start though, package is in much better shape.
Why is a document generator needing to be a runtime dependency?
Doesn't need to be a rundep. This links against qt5-base which depends on pango.
Most sources are GPL-3.0-or-later but some are still GPL-2.0-or-later. For sure nothing is licensed under GPL-3.0-only.
updated to latest gnuradio release.
all build deps are neccesarry, with run deps im not totally sure i made comments for u to understand what i did dont know if comments are good or bad
license of gnuradio is GPL3 so why not GPL3.0-or-later???
Would like the builddeps to be evaluated further. Is something needed at build time, like those python deps, or are they solely needed during runtime and thus should only be specified in the rundeps.
The building / shipping of documentation found in /usr/share/doc should be disabled as well. We typically expect users to use online documentation. If there is no cmake flag for it, doing an rm -rf $installdir/usr/share/doc should be sufficient.
Further clarification. The pkgconfigs should also be sorted as 0-9A-Za-z, e.g. Qt5Core would be first, then alsa.
The comments are not necessary and should be removed. If it wasn't necessary for building it shouldn't be included to begin with, so the builddeps are typically self-explaining.
It's a separate repo so should be packaged separately.
Uncommented rundeps should be removed to begin with.
How is a development package a requirement?
The python deps are needed at build time for cmake tests to pass, and therefore be able to compile.
the doc is not build anymore, due to removing of 2 deps.
I hope the sorting is done right :D, i have no idea.
Comments are removed
volk is now speate at https://dev.getsol.us/D10458
the devel package was stateted as requiered by the official docu, but seems obsolete
Needs a MAINTAINERS.md file containing the following contents, replacing the relevant sections.
This file is used to indicate responsibility for the maintenance of this package. Individuals on this list should be the sole modifiers of the package, excluding cases where the Solus Team may need to perform necessary rebuilds, upgrades, or security fixes. This list should not be used for any direct contact usage. If you believe this package requires a package update, follow documentation from https://getsol.us/articles/packaging/request-a-package-update/en/. In the event this package no longer becomes sufficiently maintained, Core Team reserves the right to request a new maintainer or remove this package from the repository. - REPLACEME FIRST NAME(S) LAST NAME(S) - IRC: REPLACEME - Email: REPLACEME
pkgconfigs should be sorted 0-9A-Za-z
rundeps need to be alphabetically ordered. If you use gedit, there is a gedit plugin you can enable for a sort function.