[OTR-dev] Help needed with pidgin-otr Windows (NSIS) installer

[Ariel Poliak]

The attached file contains a modified pidgin-otr.nsi, as well as the 
DialogsEx plugin that allows access to the SHBrowseForFolder dialog.

The modified file also contains a code path to potentially do an 
automated filesystem search in the future.
The code path currently just issues a MessageBox stating that the 
functionality is not currently present and falls back to manual selection.

The flow of the installation script has been changed, to get the pidgin 
path before uninstalling the old version, so that the GetPidginInstPath 
function can access the previous version's stored pidgin install directory.

It built fine under my environment (NSIS 2.46.5-Unicode).

Ariel Poliak
Network and Security Operations
HostDime.com, Inc.

On 2013-04-05 06:56, Andrew Vineyard wrote:
> Nevermind. Not as easy as I thought it would be. Still, I like a
> challenge, and will continue looking.
>
> On 4/5/2013 5:46 AM, Andrew Vineyard wrote:
>> I've messed around with NSIS a lot. While I can't say I know for certain
>> that I know everything about NSIS, I can certainly take a look and
>> figure it out. Shouldn't be too difficult though. Just have to configure
>> it so that if it doesn't find anything, it'll then ask. Simple
>> IfFileExists kind of argument in NSIS.
>>
>> On 4/5/2013 5:27 AM, otr-dev-request at lists.cypherpunks.ca wrote:
>>
>>> Message: 1
>>> Date: Thu, 4 Apr 2013 11:06:39 -0400
>>> From: Ian Goldberg <ian at cypherpunks.ca>
>>> Subject: [OTR-dev] Help needed with pidgin-otr Windows (NSIS)
>>> 	installer
>>> To: otr-dev at lists.cypherpunks.ca
>>> Message-ID: <20130404150639.GF12096 at thunk.cs.uwaterloo.ca>
>>> Content-Type: text/plain; charset=us-ascii
>>>
>>> Now and again, some Windows users point out that the pidgin-otr Windows
>>> installer doesn't know what to do if pidgin is installed in an unusual
>>> place (and doesn't have a registry entry).
>>>
>>> Ideally, it would ask the user where it is (in interactive mode) or take
>>> a command-line option (in batch mode).
>>>
>>> Does anyone know NSIS well enough to quickly make a patch to the
>>> GetPidginInstPath function in
>>> pidgin-otr/packaging/windows/pidgin-otr.nsi to support this?
>>>
>>> http://otr.git.sourceforge.net/git/gitweb.cgi?p=otr/pidgin-otr;a=blob;f=packaging/windows/pidgin-otr.nsi;h=fdcd74db93874e376252fbc140b840ebbcf56529;hb=HEAD
>>>
>>> Thanks,
>>>
>>>     - Ian
>>>
>>>
>>> ------------------------------
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pidgin-otr-nsi-new.tar.xz
Type: application/octet-stream
Size: 101380 bytes
Desc: not available
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20130405/c86770ca/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1721 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20130405/c86770ca/attachment.bin>