ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-30 01:38:55 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
a2b27135db
tahoe-lafs/windows/installer.tmpl

63 lines
3.2 KiB
Cheetah
Raw Normal View History

add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
[Setup]
installer and config - name changes
2008-02-27 02:34:39 +00:00
AppName=Allmydata 3.0
setup: use "-rNN" with NN the "revision number" instead of "-NN" with NN the "build number" in the Windows builds
2008-03-11 03:15:04 +00:00
AppVerName=Allmydata 3.0 %(major)d.%(minor)d.%(point)d-r%(revision)d
AppVersion=%(major)d.%(minor)d.%(point)d-r%(revision)d
VersionInfoVersion=%(major)d.%(minor)d.%(point)d.%(revision)d
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
AppPublisher=Allmydata Inc.
windows installer: use an allmydata logo in setup wizard
2008-03-18 23:18:07 +00:00
AppCopyright=Copyright (c) 2004-2008 Allmydata, Inc.
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
AppPublisherURL=http://www.allmydata.com/
resolve conflict in windows installer conf
2008-03-19 00:38:44 +00:00
AppSupportURL=http://support.allmydata.com/
WizardSmallImageFile=../installer.bmp
installer and config - name changes
2008-02-27 02:34:39 +00:00
DefaultDirName={pf}\Allmydata 3.0
native client - changed Windows default group name as it conflicted with the previous version
2008-02-29 01:38:38 +00:00
DefaultGroupName=Allmydata 3.0
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
; minumum version NT 4, no classic windows
MinVersion=0,4.0
Compression=lzma/max
SolidCompression=yes
windows installer build refinements this resolves problems of py2exe's modulefinder collection of sources from .zipped egg files, not by using easy_install to reach the --always-unzip option, but rather with a small tool which unpacks any zipped egg files found in misc/dependencies. this fixes the py2exe build given rollback of the easy_install stuff which had broken the unix builds. misc/hatch-eggs.py performs the honours. this also includes a misc/sub-ver.py tool which substitutes elements of the verion number for the current code base (by importing allmydata.__version__ hence make-version should be run first, and the python path carefully managed) into template files using python's string interpolation of named args from a dict as the templating syntax. i.e. %(major)d %(minor)d %(point)d %(nano)d each expand to the individual components of the version number as codified by the pyutil.version_class.Version class. there is also a %(build)s tag which expands to the string form of the whole version number. This tool is used to interpolate the automatically generated version information into the innosetup source file in a form consistent with innosetup/windows' restrictions
2008-01-15 00:53:54 +00:00
OutputDir=./installer/
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
SourceDir=dist
windows installer build refinements this resolves problems of py2exe's modulefinder collection of sources from .zipped egg files, not by using easy_install to reach the --always-unzip option, but rather with a small tool which unpacks any zipped egg files found in misc/dependencies. this fixes the py2exe build given rollback of the easy_install stuff which had broken the unix builds. misc/hatch-eggs.py performs the honours. this also includes a misc/sub-ver.py tool which substitutes elements of the verion number for the current code base (by importing allmydata.__version__ hence make-version should be run first, and the python path carefully managed) into template files using python's string interpolation of named args from a dict as the templating syntax. i.e. %(major)d %(minor)d %(point)d %(nano)d each expand to the individual components of the version number as codified by the pyutil.version_class.Version class. there is also a %(build)s tag which expands to the string form of the whole version number. This tool is used to interpolate the automatically generated version information into the innosetup source file in a form consistent with innosetup/windows' restrictions
2008-01-15 00:53:54 +00:00
SetupIconFile=../installer.ico
UninstallDisplayIcon=../amdicon.ico
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
; license file needs to be build/all dir
;LicenseFile=../license.txt
setup: use "-rNN" with NN the "revision number" instead of "-NN" with NN the "build number" in the Windows builds
2008-03-11 03:15:04 +00:00
OutputBaseFilename=Allmydata_Tahoe_Setup_v%(major)d_%(minor)d_%(point)d_r%(revision)d
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
[Files]
; contents of 'binaries' dir. (consolidated build target)
Source: "*.*"; DestDir: "{app}\Install"; Flags: restartreplace replacesameversion uninsrestartdelete
fix windows build's packaging of web templates the recent changes to webish's template lookup (to use nevow.util hence pkg_resources) to support the mac build, needs these changes to the windows build in match the new lookup path
2008-01-24 01:23:37 +00:00
Source: ".\pkg_resources\*.*"; DestDir: "{app}\Install\pkg_resources"; Flags: recursesubdirs
add winfuse plugin to installer this adds the latest build of mike's winfuse plugins, now also running as a windows service (and using the node.url, private/root_dir.cap files from the noderoot specified by the registry) into the install process.
2008-01-17 02:15:35 +00:00
Source: ".\winfuse\*.*"; DestDir: "{app}\Install\winfuse"; Flags: recursesubdirs
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
[Dirs]
Name: "{app}\noderoot"
[Icons]
; Program files entries
windows installer - changed to reflect the new StartAllmydata.exe executable that is used to launch the various pieces of the native client. Also verified that the SMB service was stopped when uninstalling.
2008-03-18 17:44:43 +00:00
Name: "{group}\Allmydata"; Filename: "{app}\Install\winfuse\StartAllmydata.exe"
Name: "{commonstartup}\Allmydata"; Filename: "{app}\Install\winfuse\StartAllmydata.exe"
updating installer for beta release
2008-02-14 04:36:09 +00:00
;Name: "{group}\Tahoe root dir (web)"; Filename: "{app}\Install\tahoe.exe"; Parameters: "webopen"
windows installer - changed to reflect the new StartAllmydata.exe executable that is used to launch the various pieces of the native client. Also verified that the SMB service was stopped when uninstalling.
2008-03-18 17:44:43 +00:00
Name: "{group}\Allmydata Help"; Filename: "http://www.allmydata.com/help"
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
[Run]
; Things performed before the final page of the installer
add winfuse plugin to installer this adds the latest build of mike's winfuse plugins, now also running as a windows service (and using the node.url, private/root_dir.cap files from the noderoot specified by the registry) into the install process.
2008-01-17 02:15:35 +00:00
Filename: "{app}\Install\tahoesvc.exe"; Parameters: "-install -auto"; Flags: runhidden
Filename: "{app}\Install\tahoe.exe"; Parameters: "create-client ""{app}\noderoot"""; Flags: runhidden
Filename: "{app}\Install\winfuse\InstallUtil.exe"; Parameters: """{app}\Install\winfuse\WinFUSE.exe"""; Flags: runhidden
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
Filename: "{app}\Install\confwiz.exe"; Flags: hidewizard
;Filename: "{app}\Install\ReadMe.txt"; Description: "View the ReadMe file"; Flags: unchecked postinstall nowait shellexec skipifdoesntexist
windows installer - changed to reflect the new StartAllmydata.exe executable that is used to launch the various pieces of the native client. Also verified that the SMB service was stopped when uninstalling.
2008-03-18 17:44:43 +00:00
Filename: "{app}\Install\winfuse\StartAllmydata.exe"; Description: "Run Allmydata"; Flags: postinstall nowait
setup: use "-rNN" with NN the "revision number" instead of "-NN" with NN the "build number" in the Windows builds
2008-03-11 03:15:04 +00:00
Filename: "http://beta.allmydata.com/welcome_install?v=%(major)d.%(minor)d.%(point)d.%(revision)d"; Description: "View the Welcome Page"; Flags: postinstall shellexec
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
[UninstallRun]
; Performed before the uninstaller runs to undo things
native client - updated to match naming for service and tray executable
2008-02-22 03:24:31 +00:00
Filename: "{sys}\net.exe"; Parameters: "stop ""Allmydata SMB"""; Flags: runhidden
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
Filename: "{sys}\net.exe"; Parameters: "stop Tahoe"; Flags: runhidden
add winfuse plugin to installer this adds the latest build of mike's winfuse plugins, now also running as a windows service (and using the node.url, private/root_dir.cap files from the noderoot specified by the registry) into the install process.
2008-01-17 02:15:35 +00:00
Filename: "{app}\Install\winfuse\InstallUtil.exe"; Parameters: "/uninstall ""{app}\Install\winfuse\WinFUSE.exe"""; Flags: runhidden
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
Filename: "{app}\Install\tahoesvc.exe"; Parameters: "-remove"; Flags: runhidden
windows installer: remove uninstall tracking, add welcome page in justin's testing, the uninstall tracking was hanging the uninstall process (on vista) for now, until we see enough need for it to warrant more detailed testing/debugging/tweaks, I'm simply disabling the call to confwiz --uninstall also this adds a 'welcome page' to the install process. once the user has installed the windows build, then the installer will open a web browser to the 'welcome page' on the website ('/welcome_install')
2008-02-14 01:17:16 +00:00
;Filename: "{app}\Install\confwiz.exe"; Parameters: "--uninstall"; Flags: runhidden
more minor build tweaks for windows tweaking version number display, and fixing a couple of small bugs
2008-01-16 00:38:06 +00:00
;Filename: "http://www.allmydata.com/redirect/uninstallsurvey.php?build=%(build)s"; Flags: shellexec
add windows installer target to build add 'windows-installer' target to top level makefile to build a windows setup.exe package using innosetup. this assumes innosetup 5 is installed in program files as normal. this doesn't include any logic to manage version numbers at this point, it's just a simple experiment to test out building an installer as yet.
2008-01-12 03:41:21 +00:00
[Registry]
Root: HKLM; Subkey: "Software\Allmydata"; Flags: uninsdeletekeyifempty
Root: HKLM; Subkey: "Software\Allmydata"; ValueType: string; ValueName: "Base Dir Path"; ValueData: "{app}\noderoot"; Flags: uninsdeletekey
Reference in New Issue Copy Permalink