[MacPorts] #43756: Application Bundle for GNURadio Companion and Wireshark
#43756: Application Bundle for GNURadio Companion and Wireshark ------------------------+------------------------------------ Reporter: sxntixgo@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: MacPorts 2.3.0 Component: ports | Version: 2.2.1 Keywords: | Port: gnuradio and wireshark ------------------------+------------------------------------ I have been trying to create an application bundle for GNURadio Companion and Wireshark manually. I was able to make Wireshark to work, but GRC's icon keep bouncing in the dock until I run a flow graph, then when the flow graph is stopped, the icon in the doc disappears. Probably it is related to the top block window that GRC uses. It would be nice that these two applications have an icon in the launchpad, just like Kile or other ports -- Ticket URL: <https://trac.macports.org/ticket/43756> MacPorts <http://www.macports.org/> Ports system for OS X
#43756: Application Bundle for GNURadio Companion and Wireshark ---------------------------------+-------------------------------- Reporter: sxntixgo@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuradio wireshark | ---------------------------------+-------------------------------- Changes (by mf2k@…): * cc: michaelld@…, opendarwin.org@…, azz_chattock@…, jeremyhu@…, css@…, egall@… (added) * version: 2.2.1 => * type: request => enhancement * port: gnuradio and wireshark => gnuradio wireshark * milestone: MacPorts 2.3.0 => Comment: The Milestone field is for use by Macports team members only, please do not set it. In the future, please Cc the port maintainers ({{{port info --maintainers gnuradio wireshark}}}). -- Ticket URL: <https://trac.macports.org/ticket/43756#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#43756: Application Bundle for GNURadio Companion and Wireshark ---------------------------------+-------------------------------- Reporter: sxntixgo@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gnuradio wireshark | ---------------------------------+-------------------------------- Changes (by mf2k@…): * cc: opendarwin.org@…, azz_chattock@…, jeremyhu@…, css@…, egall@… (removed) * cc: opendarwin.org@… (added) -- Ticket URL: <https://trac.macports.org/ticket/43756#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#43756: Application Bundle for GNURadio Companion and Wireshark ---------------------------------+-------------------------------- Reporter: sxntixgo@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: gnuradio wireshark | ---------------------------------+-------------------------------- Changes (by michaelld@…): * status: new => closed * resolution: => invalid Comment: I'm happy to learn that others are trying to create an app bundle for the GNU Radio Companion (GRC). I'm certainly encouraging of you in this regard, since I don't have time for such things right now and I think it's a cool project. I'm somewhat at a loss as to why you filed this ticket and have posted nothing beyond "this is what I tried and it didn't work". You are not directly asking for our help, nor are you providing any information / files / anything that we can help you debug. Neither GNU Radio Companion nor Wireshark provide a .app via MacPorts, so as far as I can tell, your work is outside what MacPorts provides. Unless your issue is with MacPorts itself, then I suggest you email me directly about your GRC work < michael.dickens@ettus.com > and we can talk about what you're trying to do and maybe I can help you in that specific regard -- I do not maintain Wireshark. I'm closing this ticket as invalid because I don't think it has anything to do with MacPorts per se. If you feel that the issue that you're discussing here is being caused by something that MacPorts is doing, then please reopen the ticket and explain further including attaching files and anything relevant to the ticket's issue. Otherwise, I encourage you to email the respective port maintainers directly to see what they think about helping you. -- Ticket URL: <https://trac.macports.org/ticket/43756#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts