[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4191

--- Comment #10 from Chris Maynard <christopher.maynard@xxxxxxxxx> 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.