Nmap Development mailing list archives

RE: windows installer and COPYING


From: "Rob Nicholls" <robert () everythingeverything co uk>
Date: Tue, 11 Dec 2007 19:05:58 -0000

If it's decided that a second version could be maintained purely for the
Windows setup file, as it's a file that shouldn't change that often, it
could perhaps be a pretty looking RTF file (that doesn't necessarily have to
be copied into the installation folder?), as the NSIS installer will happily
display that as well as text files (e.g. replace "..\..\COPYING" with
"..\..\COPYING-WIN32.RTF" or "..\..\COPYING.RTF" and drop the new file in
the same folder as COPYING et al). I must admit I haven't really touched NSI
files since Jan 06, back when I was modifying the old BitTorrent 4.x client.
While the NSI file's (possibly) being played with, I think it should be
possible to use the .ico file to give the setup.exe an nmap icon (!define
MUI_ICON "..\icon1.ico").

I just spotted that COPYING still says "1996-2006" at the start, perhaps
that should say 2007? Or can we be a little bit proactive and update it to
say 2008? ;)

Rob

-----Original Message-----
From: jah [mailto:jah () zadkiel plus com] 
Sent: 11 December 2007 18:25
To: nmap-dev
Subject: Re: windows installer and COPYING

<snip>

Aye to that too, but what I had in mind was an nsis friendly version of 
COPYING with no breaks except for paragraphs and bullet lists and which 
would hopefully wrap inside the field at all resolution/font-size 
combinations.  This of course would mean two versions of COPYING to 
maintain, but the alternative would be to always have some combination 
that breaks the formatting.  Unless, that is, there's another 
alternative (like a one liner)...

jah

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


Current thread: