Bump GNU Radio from 3.2 to 3.2.2; add gnuradi-examples; fix for usrp port for libusb-legacy

[michaelld (Michael Dickens)]

Some ports / components of GNU Radio 3.2 (what MacPorts current provides) will not configure or compile right now. These changes bump GNU Radio to 3.2.2, as well as fix those issues. Note that the GNU Radio ports will not yet configure or compile under 10.6; the current GNU Radio GIT master already contains those fixes -- and they will be part of the next number release.

I'm attaching not the diffs, but the whole file structure of the GNU Radio ports including the addition of gnuradio-examples. I can provide diffs, but some files are removed and others added -- so I really don't know the best way to go; hence providing everything.

[michaelld (Michael Dickens)]

GNU Radio 3.2.2 Portfiles & related

[michaelld (Michael Dickens)]

I just uploaded a new set of Portfiles & related, which fixes the SWIG dependency (from 'swig' to 'swig-python'). I understand that this port has no owner ... any way I can become that owner so that these changes can be entered more quickly?

[mf2k (Frank Schima)]

Replying to mlk@…:

I just uploaded a new set of Portfiles & related, which fixes the SWIG dependency (from 'swig' to 'swig-python'). I understand that this port has no owner ... any way I can become that owner so that these changes can be entered more quickly?

If you become maintainer that would be very helpful. However, you still will not be able to commit the changes and the long delays will continue. One thing that would be helpful is to post ​unified diffs of the portfiles instead. In order to commit changes, you would need to apply for ​macports membership.

[mf2k (Frank Schima)]

Also, since I am on Snow Leopard, I won't be able to build this version and so I will not commit it.

[michaelld (Michael Dickens)]

(1) I've applied for membership so-as to keep GNU Radio up to date. If accepted, I'll get these updates in place ASAP.

(2) I usually do use 'diff -u' (or, 'git diff' these days), but in this case because files were removed and added, along with the usual changes to the many portfiles, it seemed simpler to just tarball up the whole shebang. In my experience working with GNU Radio, working with diffs is about as difficult as working with a tarball of changes. That said, we also work with GIT, which makes this process very simple -- it was more difficult with CVS and SVN, but we still did it. Certainly if we can do it, so can MacPorts' folks -- even if it's not the preferred method.

(3) So, I thought one of MacPorts' "claims to fame" is providing compatibility with 10.4 and up through the latest Mac OS version. I can understand if that's been changed to 10.5 and up, but not "just" 10.6 yet, yes? If 10.5 and up still, then what can I do (beyond (1)) to get someone with 10.5 to review my changes (even if I did (2))?

[ryandesign (Ryan Carsten Schmidt)]

I see you committed the update in r63421. You still need to commit the patches for usrp.

[michaelld (Michael Dickens)]

Thanks for pointing that out; I missed those when I merged my local dports with the macports SVN trunk.

[michaelld (Michael Dickens)]

r63421, r63422, r63423, and r63424 resolve the issues of this ticket.

[ryandesign (Ryan Carsten Schmidt)]

Great, thanks. In the future, don't forget to put the ticket number in the commit message. I've gone and fixed this in the commits you mention above.

[michaelld (Michael Dickens)]

Didn't know I needed to; I will in the future; thanks for correcting for me.