Howdy guys.
I see some work around getting gr-osmosdr working nicely with GR 3.8, but have there been any discussions around GR 3.9 (really current 'master')?
I recently decided to pick GNU Radio back up and hook up my rtl dongle. In particular, I wanted to dust off my C++ chops that I haven't been able to exercise in my current $DAYJOB. Naturally then I started with GNU Radio master! It looks like one major change is that they have replaced swig with pybind, which means that the current gr-osmosdr can't even begin to work. So has there been any discussion about the porting effort necessary to move it over?
I'm interested in starting to poke at getting it working under current GR 3.9/master, but had a few questions before I started:
1) Has anyone else started on the changes that I could coordinate with? 2) Is there generally any attempt at tracking gr master, or do you typically only target release branches? 3) Am I putting the cart before the horse and really need to focus any of my willingness to help on getting the GR 3.8 solid (if it isn't already)?
Thanks for time, Troy
- Is there generally any attempt at tracking gr master, or do you typically only target release branches?
Historically, we only target release branch. "Master" only gets supported when the first "rc" comes out and the GR API is declared stable.
Once the new stable release come it becomes the only supported one and what gr-osmosdr 'master' targets. The "old" release becomes a branch and pretty much frozen.
Now Hoerchen who's taking over gr-osmosdr may decide to change that scheme ... up to him.
Cheers,
Sylvain
On Tue, Aug 11, 2020 at 2:52 AM Sylvain Munaut 246tnt@gmail.com wrote:
Historically, we only target release branch. "Master" only gets supported when the first "rc" comes out and the GR API is declared stable.
Yeah that makes perfect sense. Who knows what more changes happen on GR master branch before they cut a release? Once I thought about a bit I realized it would be trying to constantly hit a moving target.
Now Hoerchen who's taking over gr-osmosdr may decide to change that scheme ... up to him.
Ah excellent, that answers another question I had and didn't ask, whether anyone had taken up the project lead mantle. Good to hear. I'm sure that the current process is the most reasonable one. If I really want to give it a go, I can always just have a separate branch with no expectation of hitting master until after GR 3.9 hits.
Thanks for the response! Troy
Hi Sylvain, list.
On Tue, Aug 11, 2020 at 2:52 AM Sylvain Munaut 246tnt@gmail.com wrote: ... snip ...
Now Hoerchen who's taking over gr-osmosdr may decide to change that scheme ... up to him.
Could anyone give any update on the gr-osmosdr situation? I don't track the project closely, but a quick search doesn't turn up any posts from a Hoerchen to this list.
Given the number of pending patches to gr-osmosdr, would it be helpful to have more than just one maintainer on the project?
Are there any plans yet for merging patches, or a capacity-level with regard to how many it is helpful to bring on board at first, or what could be done to them to ease consideration?
Thanks so much, Karl Semich
Hi,
Given the number of pending patches to gr-osmosdr, would it be helpful to have more than just one maintainer on the project?
What pending patches ? All the ones that have been sent here (and are actually mergeable) have been merged beginning of the month by Hoerchen according to the git logs.
Cheers,
Sylvain
I don't have access to the git not much web for now, but I am very surprised by what you say. Earlier an extensive list of forks was posted here, all with unmerged fixes to address, with no reply to the post. Over the past couple years, there was one month when I was the only person posting to this list, and all my posts were patches that still have received no reply.
Thanks for pointing me towards the git history to find Hoerchen.
On Tue, Aug 25, 2020, 12:10 PM Sylvain Munaut 246tnt@gmail.com wrote:
Hi,
Given the number of pending patches to gr-osmosdr, would it be helpful to have more than just one maintainer on the project?
What pending patches ? All the ones that have been sent here (and are actually mergeable) have been merged beginning of the month by Hoerchen according to the git logs.
Cheers,
Sylvain
On Aug 25, 2020 12:10 PM, "Sylvain Munaut" 246tnt@gmail.com wrote:
Hi,
Given the number of pending patches to gr-osmosdr, would it be helpful to have more than just one maintainer on the project?
What pending patches ? All the ones that have been sent here (and are actually mergeable) have been merged beginning of the month by Hoerchen according to the git logs.
Cheers,
Sylvain
We don't go looking forks ... if something is not posted to this ML, we won't see it.
Anything posted or submitted from before the 3.8 port, was also discarded, when I did the adaptation I didn't go and look in the archive to see if there was anything still relevant ... If it was I figured the author would rebase the patch to apply cleanly onto the new branch and repost if he cared and if he didn't then it must not have been that important.
Cheers,
Sylvain
-
Karl Semich -
Karl Semich -
Sylvain Munaut -
Troy Curtis Jr