John,
Just wanted to touch base and see where you are with the Wireshark Portable that you alluded to in another post.
I contributed the U3 packaging for Wireshark and have recently been working on a Portable Apps version - before seeing your comment. (Is there somewhere else I could find out what was in progress?)
My version is very simple - just packaging, no code changes required to WS itself. It takes the same simple/dumb approach for WinPcap as the U3 version - just runs the installer if it can't detect WinPcap is already installed, and removes it when it's done.
I'm still developing this and haven't checked it into the main WS development tree yet.
If your version is imminent, I'll hold fire developing it any further and see what you've done. Depending on how you like to do things, I could incorporate the packaging into the WS source code and get the buildbot building regular Portable App distributions, as well as the U3 distributions.
Graeme
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
That is the dumb way. It's not actually portable at all. However, I'll let John comment on it and explain.
"If you're not part of the solution, you're part of the precipitate."
It's actually the only way. Wireshark uses a device driver. So it has to be installed and uninstalled.
As for working on it, ping me at the contact address. It would probably be best for Wireshark to maintain it themselves rather than having a separate launcher. I can assist with PortableApps.com Format and an installer, though.
Sometimes, the impossible can become possible, if you're awesome!
I forgot about that little detail
"If you're not part of the solution, you're part of the precipitate."
John,
I interpreted the "contact address" as developers_developers, and sent the nsi files etc there on 1st Nov. Just wanted to check that was the right address and you received them?
Thanks,
Graeme