I contacted the gnuradio IRC channel. They are changing their development model, and porting the application to Python3 and Qt5. This is not something that will happen soon though, as these updates are not coming before version 3.8.0.0, that is, by the end of the year.
What should I do @DataDrake? Can I package it or should I wait for the newer version? I want you to know that wx-based GUI has been deprecated so it may have issues or missing features, so this is not a real workaround.

There ;-)

Yeah, let's wait for the Qt5 release. I know it sucks, but I'd rather not ship broken software.

Please allow me to upload my current package.yml in order not to redo useless work in future ?

I was trying to learn how to package applications for Solus and I ended up creating a package for Volk, a library used to optimise GNU Radio

GR's feature freeze is on 10 January 2019. v3.8 will likely be out by the end of that month.

Release set for Fall 2019: https://wiki.gnuradio.org/index.php/3.8

According to my knowledge, August is not in Fall, but yeah we have a release :P

When people use seasons as release dates GRRR. Seasons are not global!

This supports Qt5 now AFAICT.

Hello,
I was able to create a working build file, and i would like to maintain gnuradio for further updates, BUT i have no experience.

Thanks
Valentin

Few tips, take a look at how other package.xml are structured. The release tag is the current published version in the Solus repos, as it doesn't exist yet, this should be 1.

If a -devel package has a package config, you should use this instead. You can find this out by using eopkg info <devel package name> ie eopkg info qt5-base-devel you would use pkgconfig(Qt5Core)

Libraries used at build time are linked (see pspec_x86_64.xml and abi_used_libs) If listed there, there is no need to include them in rundep

I don't understand how your package.yml worked :/

Any-ways, I built it locally, but can't see how to test it and my internet has been driving me crazy, so I gave up on it. I uploaded the packaging to gitlab, as it might be useful to someone.

https://gitlab.com/clivejo/gnuradio

Hello,

The yml works fine for me with solbuild (i dont use unstable). I updated it to use pkgconfig as often as possible.

There are runtimedeps needed, as there are some dependencies, which are not needed in built-time, but in runtime.

here is the updated yml and the pspec file.

Also, pkgconfig always come first in the list and ordered alphabetical.

license, summary, component, description tags usually come after the source tag and before builddeps. See https://getsol.us/articles/packaging/package.yml/en/ for the structure.

Also the licence needs to be from the following list - https://spdx.org/licenses/ so should be either GPL-3.0-only or GPL-3.0-or-later depending on what is applicable.

In T5589#173836, @VValterKing wrote:

The yml works fine for me with solbuild (i dont use unstable). I updated it to use pkgconfig as often as possible.

Odd it failed for me with [BuildDep] Unknown build deps: python3-gobject

Ah, they were merged https://dev.getsol.us/source/python-gobject/ , please update the build dep to python-gobject

Removed uploaded files. Please submit a patch following the appropriate method documented on our Help Center, should you be interested in becoming the maintainer for this.