[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 Gerald Combs ger...@wireshark.org changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #18 from Gerald Combs ger...@wireshark.org --- Wireshark 1.99.0 is out and was built using the current PortableApps toolchain. I can install it and run it without any issues in PA Platform 12.0.5. Marking as fixed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #17 from Gerrit Code Review gerrit-do-not-re...@wireshark.org --- Change 3962 had a related patch set uploaded by Gerald Combs: Fix PortableApps packaging. https://code.wireshark.org/review/3962 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #15 from Chris Maynard christopher.mayn...@gtech.com 2010-12-29 12:50:07 PST --- (In reply to comment #14) The absolute easiest thing to do is to use the PA.c Installer to generate each package as it will generate all the updated code on the fly. Then you only need to keep PA.c Installer up to date and not NSIS + plugins + PA.c NSIS code, etc. For now, I committed some changes to at least build the portableapps installer using nsis unicode, since Gerald loaded it on the buildbot. If we switch to using the PA.c Installer, then other changes will be needed. Keep in mind that we create normal Windows installers as well as a U3 installer in addition to the portableapps installer, and we haven't switch to using nsis unicode for those, so we still need to keep the nsis and FindProc.dll plugin updated. I'm not sure switching to PA.c is any easier, but if you think it is, maybe you could fully describe what other changes are needed or better yet, submit a patch that details the exact changes required. As for using the NSIS within PA.c Installer to generate the launcher, that's a possibility. Last I checked, I think everything in your launcher is included in our abbreviated NSIS install within PA.c Installer. So what do you need me to work on or review at this point? I think we'll miss our 31 days of appness for getting this out (new app every day this month) but we can do it as part of our January blitz. I think the ideal thing would be for you to submit a patch that details exactly what else we need. I know the PA.c Installer requires a help.html file, so that needs to be created and could be useful whether we switch to the PA.c Installer or not, but I don't know what else is needed at this point. You'll have to forgive my ignorance on this as I'm not all that familiar with portableapps. Perhaps another Wireshark core developer could assist here where I'm lacking understanding? -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #14 from John T. Haller bugzil...@johnhaller.com 2010-12-27 22:07:18 PST --- (In reply to comment #13) John, if we want to go with the first one, do you see any issues with that? The absolute easiest thing to do is to use the PA.c Installer to generate each package as it will generate all the updated code on the fly. Then you only need to keep PA.c Installer up to date and not NSIS + plugins + PA.c NSIS code, etc. As for using the NSIS within PA.c Installer to generate the launcher, that's a possibility. Last I checked, I think everything in your launcher is included in our abbreviated NSIS install within PA.c Installer. So what do you need me to work on or review at this point? I think we'll miss our 31 days of appness for getting this out (new app every day this month) but we can do it as part of our January blitz. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #10 from Chris Maynard christopher.mayn...@gtech.com 2010-12-15 08:41:11 PST --- (In reply to comment #9) Yes, you just feed a directory as a command line argument to PortableApps.comInstaller.exe and it'll create the WireSharkPortable_x.x.x.paf.exe in the parent directory. OK. It looks like other makefile.nmake changes will be needed as well though, once the switch to Unicode NSIS is made. There are a couple more plugins that would be needed and you'd need NSIS Unicode instead of NSIS. I'm unsure if you're using NSIS Proper (ANSI) or NSIS Unicode yet, but if the former, I would suggest switching to NSIS Unicode as Mozilla, OpenOffice.org and others have done. OK, I was thinking of only the extra plugins that don't come with NSIS by default. FindProc is the only extra one currently used right now (downloaded as part of the setup from http://anonsvn.wireshark.org/wireshark-win32-libs/tags/2010-10-10/packages/), but I see that the PA.c Installer 2.0.7 already includes it with the Unicode NSIS, so I guess we wouldn't need to have it downloaded separately as part of the setup anymore. Personally I'm now running NSIS 2.46 from http://nsis.sourceforge.net/Main_Page, but the Windows-XP-x86 buildbot is currently using v2.44. If we need the Unicode NSIS (I got it from http://www.scratchpaper.com/) for PortableApps, then either we need to have both versions installed and get them to play nice together with some new setting in config.nmake (MAKENSIS and UMAKENSIS, for example), or we just switch to Unicode NSIS for creating all the Windows installers (normal, U3 and PortableApps). IMO, I think it's better and easier to only require one. But if that's the case - switch to Unicode NSIS for all installers - then why bother with the PA.c Installer? Is there some other compelling reason to do so? Unfortunately, it seems that Unicode NSIS still doesn't include the FindProc.dll by default, so we'll still need to download it separately. I don't think that alone is a compelling enough reason to require both Unicode NSIS and PA.c Installer though. Ok, I'll put together what's needed in the current release to get AppInfo up to snuff. I made a few quick changes and was able to create a WiresharkPortable installer using the PA.c Installer. I'll post my small changes to appinfo.tmpl and installer.ini. I had to fake a simple help.html file as the PA.c installer complained and wouldn't run without one. I think we need to wait on makefile.nmake changes until we decide on the Unicode NSIS switch since it will break the buildbot if not coordinated properly. Other changes will be needed as well if we switch, such as the documentation for the developer's guide, etc. When :) You'll get your own page on PortableApps.com at the URL you mentioned. You'd release it just as you do now on your own servers and we'll link to it and update that link as you release each new version, also announcing it to our users via RSS/twitter/facebook and our updater. We keep a database of all apps for our updater and it'll use your server as well. We'll monitor your RSS feed for update announcements and typically have it posted on our page the same day. We can even link into your downloads on your site from your own users to help keep stats and show you properly in the 'popular apps' charts we'll be debuting. You can have as many versions as you'd like on your site, we typically only show the current release on PA.c. I like your optimism! All of this sounds good to me. Gerald et al may have other questions/concerns. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #11 from Chris Maynard christopher.mayn...@gtech.com 2010-12-15 08:55:33 PST --- Created an attachment (id=5618) -- (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5618) An initial patch for illustration, likely not complete. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #12 from Gerald Combs ger...@wireshark.org 2010-12-15 11:31:40 PST --- (In reply to comment #10) Personally I'm now running NSIS 2.46 from http://nsis.sourceforge.net/Main_Page, but the Windows-XP-x86 buildbot is currently using v2.44. If we need the Unicode NSIS (I got it from http://www.scratchpaper.com/) for PortableApps, then either we need to have both versions installed and get them to play nice together with some new setting in config.nmake (MAKENSIS and UMAKENSIS, for example), or we just switch to Unicode NSIS for creating all the Windows installers (normal, U3 and PortableApps). IMO, I think it's better and easier to only require one. But if that's the case - switch to Unicode NSIS for all installers - then why bother with the PA.c Installer? Is there some other compelling reason to do so? Unfortunately, it seems that Unicode NSIS still doesn't include the FindProc.dll by default, so we'll still need to download it separately. I don't think that alone is a compelling enough reason to require both Unicode NSIS and PA.c Installer though. It looks like Unicode NSIS installs into c:\Program Files\NSIS\Unicode by default. Could we add a MAKENSIS_UNICODE definition to config.nmake and require it for the PA package? I upgraded NSIS on the XP to 2.46 and installed NSIS Unicode 2.46. When :) You'll get your own page on PortableApps.com at the URL you mentioned. You'd release it just as you do now on your own servers and we'll link to it and update that link as you release each new version, also announcing it to our users via RSS/twitter/facebook and our updater. We keep a database of all apps for our updater and it'll use your server as well. We'll monitor your RSS feed for update announcements and typically have it posted on our page the same day. We can even link into your downloads on your site from your own users to help keep stats and show you properly in the 'popular apps' charts we'll be debuting. You can have as many versions as you'd like on your site, we typically only show the current release on PA.c. I like your optimism! All of this sounds good to me. Gerald et al may have other questions/concerns. John, we have a PAD file at http://www.wireshark.org/wireshark-pad.xml for the Win32 installer which is updated as part of the release process. I can add one for the PA package if it helps. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #13 from Chris Maynard christopher.mayn...@gtech.com 2010-12-15 12:56:47 PST --- (In reply to comment #12) It looks like Unicode NSIS installs into c:\Program Files\NSIS\Unicode by default. Could we add a MAKENSIS_UNICODE definition to config.nmake and require it for the PA package? Yes, but what should MAKENSIS_UNICODE be set to? Do you prefer to use the Unicode NSIS from http://www.scratchpaper.com/ or the one bundled with and extracted from the PA.c Installer available from http://portableapps.com/apps/development/portableapps.com_installer? John, if we want to go with the first one, do you see any issues with that? -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #8 from Chris Maynard christopher.mayn...@gtech.com 2010-12-14 11:24:17 PST --- (In reply to comment #7) The installer is now self-contained and, while it will generate NSIS code you could drop into your build system, it will only work with NSIS Unicode with a specific set of plugins. As such, it's best to use the PA.c Installer to compile your PAF.exe directly. This works on a Windows box or a *nix/*bsd box with a current version of Wine installed. I'm not entirely sure how this will change the builds for us. Currently, it looks like only the Windows-XP-x86 buildbot is building the Wireshark portableapps package (http://buildbot.wireshark.org/trunk/waterfall), so I'm guessing it means installing the PA.c Installer on it, then some changes to the portableapps makefile.nmake file ... or something along those lines? I think the only NSIS plugin we're using is FindProcDLL (http://nsis.sourceforge.net/FindProcDLL_plug-in). Is this one among those that will work? If so, would it be possible to have the option of creating the portableapps installer either way - i.e., keep creating it the way it's been done thus far, or create it with the PA.c Installer? I don't know if this would really be necessary but just thought I'd ask. The only other things needing changes would be the files in AppInfo as we've updated the format. The installer entirely generates the appropriate NSIS code and compiles it using a built-in pre-configured copy of NSIS Unicode based on that. Would it be best to do this as a proposed patch right in this bug report? Yes, that would be great! Once that's done, we can get Wireshark listed on PortableApps.com and exposed to our millions of users. Sounds good. If/when Wireshark becomes listed, where would the installer home be? I guess a new page would need to be created as http://portableapps.com/apps/internet/wireshark_portable, and then the installer would need to be copied over to sourceforge.net? How do you foresee that working as each new release comes out? Also, I assume only the latest stable portableapps version would be listed, is that correct? For older versions, or for the latest unstable versions, would there exist any link back to www.wireshark.org for obtaining those? Thanks John. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #9 from John T. Haller bugzil...@johnhaller.com 2010-12-14 14:39:24 PST --- (In reply to comment #8) I'm not entirely sure how this will change the builds for us. Currently, it looks like only the Windows-XP-x86 buildbot is building the Wireshark portableapps package (http://buildbot.wireshark.org/trunk/waterfall), so I'm guessing it means installing the PA.c Installer on it, then some changes to the portableapps makefile.nmake file ... or something along those lines? Yes, you just feed a directory as a command line argument to PortableApps.comInstaller.exe and it'll create the WireSharkPortable_x.x.x.paf.exe in the parent directory. I think the only NSIS plugin we're using is FindProcDLL (http://nsis.sourceforge.net/FindProcDLL_plug-in). Is this one among those that will work? If so, would it be possible to have the option of creating the portableapps installer either way - i.e., keep creating it the way it's been done thus far, or create it with the PA.c Installer? I don't know if this would really be necessary but just thought I'd ask. There are a couple more plugins that would be needed and you'd need NSIS Unicode instead of NSIS. I'm unsure if you're using NSIS Proper (ANSI) or NSIS Unicode yet, but if the former, I would suggest switching to NSIS Unicode as Mozilla, OpenOffice.org and others have done. Yes, that would be great! Ok, I'll put together what's needed in the current release to get AppInfo up to snuff. Sounds good. If/when Wireshark becomes listed, where would the installer home be? I guess a new page would need to be created as http://portableapps.com/apps/internet/wireshark_portable, and then the installer would need to be copied over to sourceforge.net? How do you foresee that working as each new release comes out? Also, I assume only the latest stable portableapps version would be listed, is that correct? For older versions, or for the latest unstable versions, would there exist any link back to www.wireshark.org for obtaining those? When :) You'll get your own page on PortableApps.com at the URL you mentioned. You'd release it just as you do now on your own servers and we'll link to it and update that link as you release each new version, also announcing it to our users via RSS/twitter/facebook and our updater. We keep a database of all apps for our updater and it'll use your server as well. We'll monitor your RSS feed for update announcements and typically have it posted on our page the same day. We can even link into your downloads on your site from your own users to help keep stats and show you properly in the 'popular apps' charts we'll be debuting. You can have as many versions as you'd like on your site, we typically only show the current release on PA.c. Thanks John. Sure thing. Looking forward to getting Wireshark on some more USB drives. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #7 from John T. Haller bugzil...@johnhaller.com 2010-12-09 07:18:19 PST --- (In reply to comment #6) John, any update? BTW, I see the installer is now at 2.0.6. I'm curious as to how many updates there have been since you went to 1.0, and what impact, if any, each one has? The installer is now self-contained and, while it will generate NSIS code you could drop into your build system, it will only work with NSIS Unicode with a specific set of plugins. As such, it's best to use the PA.c Installer to compile your PAF.exe directly. This works on a Windows box or a *nix/*bsd box with a current version of Wine installed. The only other things needing changes would be the files in AppInfo as we've updated the format. The installer entirely generates the appropriate NSIS code and compiles it using a built-in pre-configured copy of NSIS Unicode based on that. Would it be best to do this as a proposed patch right in this bug report? Once that's done, we can get Wireshark listed on PortableApps.com and exposed to our millions of users. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #6 from Chris Maynard christopher.mayn...@gtech.com 2010-12-01 11:15:34 PST --- (In reply to comment #5) John, can you be a little more specific about the changes that need to be made? E.g. how should the PortableApps.com Installer be run to create the package? John, any update? BTW, I see the installer is now at 2.0.6. I'm curious as to how many updates there have been since you went to 1.0, and what impact, if any, each one has? -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 Jaap Keuter jaap.keu...@xs4all.nl changed: What|Removed |Added CC||ger...@wireshark.org --- Comment #1 from Jaap Keuter jaap.keu...@xs4all.nl 2009-11-13 12:32:50 PDT --- Should this be addressed for 1.2.4 ? -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #2 from John T. Haller bugzil...@johnhaller.com 2009-11-13 12:35:49 PDT --- Hopefully it can for 1.2.4. As soon as it is, we can list it on PortableApps.com and start promoting it to our users. The older installer won't work with the updater we're releasing next week. If we want to do the actual installer build manually for right now, we can. Like I said, all the files and configurations needed are already in 1.2.3. It just needs to be compiled using the current PortableApps.com Installer here: http://portableapps.com/apps/development/portableapps.com_installer -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #3 from Gerald Combs ger...@wireshark.org 2009-11-13 16:41:38 PDT --- It shouldn't be a problem to keep the installer generator up to date on the build server. What changes need to be made in SVN (e.g. to the makefile)? -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
[Wireshark-bugs] [Bug 4191] Wireshark Portable installer outdated
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191 --- Comment #4 from John T. Haller bugzil...@johnhaller.com 2009-11-13 17:35:48 PDT --- No changes need be made from 1.2.3 (other than updating the PackageVersion and DisplayVersion in App\AppInfo\appinfo.ini, which I believe is already happening with the build system). So SVN should be just fine. The installer is generated from the info in appinfo.ini and the other files in the AppInfo directory. This was updated already from a previous bug and is now up to date. The only thing we may want to explore is any plugins that users might add and what directory they are in. The current Wireshark Portable installer doesn't take this into account, so the updates I provided now in SVN don't either. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Sent via:Wireshark-bugs mailing list wireshark-bugs@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-bugs Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
