https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191
--- Comment #12 from Gerald Combs <gerald@xxxxxxxxxxxxx> 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.