build an .exe installer for 64-bit Windows 7 (and preferably 8) #195

Closed
opened 2007-10-29 17:15:35 +00:00 by zooko · 15 comments
zooko commented 2007-10-29 17:15:35 +00:00
Owner

My dad would love to see some new grand-children movies. I would love for there to be a package for Tahoe on Windows that was simple enough to install that he could install it on his home computer.

The starting point should probably be to find out how well setuptools and py2exe have grown together since last we looked...

http://peak.telecommunity.com/DevCenter/setuptools
http://www.py2exe.org/index.cgi/ExeWithEggs
http://www.py2exe.org/index.cgi/News

My dad would love to see some new grand-children movies. I would love for there to be a package for Tahoe on Windows that was simple enough to install that he could install it on his home computer. The starting point should probably be to find out how well setuptools and py2exe have grown together since last we looked... <http://peak.telecommunity.com/DevCenter/setuptools> <http://www.py2exe.org/index.cgi/ExeWithEggs> <http://www.py2exe.org/index.cgi/News>
tahoe-lafs added the
packaging
major
enhancement
0.6.1
labels 2007-10-29 17:15:35 +00:00
zooko commented 2007-10-29 17:16:16 +00:00
Author
Owner

See also ticket #182 -- user-friendly installer for Mac -- for my Mom!

See also ticket #182 -- user-friendly installer for Mac -- for my Mom!
zooko commented 2007-11-01 18:07:03 +00:00
Author
Owner

We're focussing on an imminent v0.7.0 (see the roadmap) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.

We're focussing on an imminent v0.7.0 (see [the roadmap](http://allmydata.org/trac/tahoe/roadmap)) which hopefully has [#197 #197 -- Small Distributed Mutable Files] and also a fix for [#199 #199 -- bad SHA-256]. So I'm bumping less urgent tickets to v0.7.1.
zooko commented 2007-11-13 18:26:43 +00:00
Author
Owner

We need to choose a manageable subset of desired improvements for [ http://allmydata.org/trac/tahoe/milestone/0.7.1 v0.7.1], scheduled for two week hence, so I'm bumping this one into v0.7.2, scheduled for mid-December.

We need to choose a manageable subset of desired improvements for [ <http://allmydata.org/trac/tahoe/milestone/0.7.1> v0.7.1], scheduled for two week hence, so I'm bumping this one into [v0.7.2](http://allmydata.org/trac/tahoe/milestone/0.7.2), scheduled for mid-December.
tahoe-lafs added
0.7.0
and removed
0.6.1
labels 2007-11-13 18:26:43 +00:00
zooko commented 2007-12-21 18:46:46 +00:00
Author
Owner

See tickets #242 -- "binary package for win32" and #243 -- "package including all dependencies for win32" which are two steps leading up to this ticket.

See tickets #242 -- "binary package for win32" and #243 -- "package including all dependencies for win32" which are two steps leading up to this ticket.
zooko commented 2008-01-04 19:28:53 +00:00
Author
Owner

Brian wrote:

"* add windows-specific code to the installer to automatically create a node, and run it as a service. The install process should have a checkbox (defaulting to Yes) to do the service thing. The install should also create a "tahoe" executable (for command-line tools like 'tahoe ls'), and a "tahoe-client" executable (which just runs the client). The goal for this is to allow a user to run multiple nodes in separate directories, or to just get the default node and have it automatically start. We also need configuration control panels to set an Introducer."

Brian wrote: "* add windows-specific code to the installer to automatically create a node, and run it as a service. The install process should have a checkbox (defaulting to Yes) to do the service thing. The install should also create a "tahoe" executable (for command-line tools like 'tahoe ls'), and a "tahoe-client" executable (which just runs the client). The goal for this is to allow a user to run multiple nodes in separate directories, or to just get the default node and have it automatically start. We also need configuration control panels to set an Introducer."
tahoe-lafs modified the milestone from 0.9.0 (Allmydata 3.0 final) to 0.8.0 (Allmydata 3.0 Beta) 2008-01-09 01:10:51 +00:00
zooko commented 2008-01-10 20:26:01 +00:00
Author
Owner

Rob has made some good progress on this already!

Rob has made some good progress on this already!
zooko commented 2008-03-08 01:33:26 +00:00
Author
Owner

I think Rob has pretty much done this, as well as:

  • #243 (package including all dependencies for win32)
  • #242 (binary package for win32)

but perhaps not yet

Rob: please close these tickets as appropriate.

I think Rob has pretty much done this, as well as: * #243 (package including all dependencies for win32) * #242 (binary package for win32) but perhaps not yet * #194 (README.w32) Rob: please close these tickets as appropriate.
tahoe-lafs modified the milestone from 0.8.0 (Allmydata 3.0 Beta) to 0.9.0 (Allmydata 3.0 final) 2008-03-08 01:33:26 +00:00
Author
Owner

the 'make windows-installer' build target takes a py2exe build (c.f. #242) and makes a double-clickable installer for windows. it depends upon innosetup 5 to build the installer.

this includes all the binaries mentioned in #242, and runs the confwiz by default upon install. thus the user, upon install, is prompted to log into or create and account, and the machine's tahoesvc node is thus configured.

this installer also includes the 'winfuse' subsystem and the 'allmydatatray.exe' which provide, respectively, an SMB interface to the tahoe filesystem, allowing browsing and use of the fs via windows explorer and arbitrary apps, and a small system-tray ui widget making it easy to start/stop the tahoe service, access that SMB share ('drive') and to launch the built in windows backup facilities.

the 'make windows-installer' build target takes a py2exe build (c.f. #242) and makes a double-clickable installer for windows. it depends upon innosetup 5 to build the installer. this includes all the binaries mentioned in #242, and runs the confwiz by default upon install. thus the user, upon install, is prompted to log into or create and account, and the machine's tahoesvc node is thus configured. this installer also includes the 'winfuse' subsystem and the 'allmydatatray.exe' which provide, respectively, an SMB interface to the tahoe filesystem, allowing browsing and use of the fs via windows explorer and arbitrary apps, and a small system-tray ui widget making it easy to start/stop the tahoe service, access that SMB share ('drive') and to launch the built in windows backup facilities.
tahoe-lafs added the
fixed
label 2008-03-12 19:29:00 +00:00
robk closed this issue 2008-03-12 19:29:00 +00:00
zooko commented 2013-11-02 00:01:13 +00:00
Author
Owner

This Windows package has long since bit-rotted due to being unmaintained and not having tests.

This Windows package has long since bit-rotted due to being unmaintained and not having tests.
tahoe-lafs removed the
fixed
label 2013-11-02 00:01:13 +00:00
zooko reopened this issue 2013-11-02 00:01:13 +00:00
tahoe-lafs modified the milestone from 0.9.0 (Allmydata 3.0 final) to soon 2014-09-25 15:56:27 +00:00
zooko commented 2014-09-25 16:02:02 +00:00
Author
Owner

#1093 was a duplicate of this, with detailed reports from multiple people who attempted to build .exe's.

#1093 was a duplicate of this, with detailed reports from multiple people who attempted to build .exe's.
tahoe-lafs changed title from user-friendly installer for Windows -- for my Dad! to build an .exe installer for Windows 7 (and preferably 8) 2014-09-25 16:26:00 +00:00
tahoe-lafs changed title from build an .exe installer for Windows 7 (and preferably 8) to build an .exe installer for 64-bit Windows 7 (and preferably 8) 2014-09-25 16:27:42 +00:00
daira commented 2014-10-28 19:06:11 +00:00
Author
Owner
Currently working on this in the <https://github.com/tahoe-lafs/tahoe-lafs/commits/195-windows-packaging-2> branch.
tahoe-lafs modified the milestone from soon to 1.11.0 2014-10-28 19:06:11 +00:00
tahoe-lafs modified the milestone from 1.10.1 to 1.11.0 2015-05-19 16:38:37 +00:00
daira commented 2015-05-30 18:14:05 +00:00
Author
Owner

Current branch is https://github.com/tahoe-lafs/tahoe-lafs/commits/195.windows-packaging.10. This is broken at the moment and there's little point in wider testing yet; I intend to finish it after the release of v1.10.1.

Current branch is <https://github.com/tahoe-lafs/tahoe-lafs/commits/195.windows-packaging.10>. This is broken at the moment and there's little point in wider testing yet; I intend to finish it after the release of v1.10.1.
warner commented 2016-03-22 05:02:52 +00:00
Author
Owner

Milestone renamed

Milestone renamed
tahoe-lafs modified the milestone from 1.11.0 to 1.12.0 2016-03-22 05:02:52 +00:00
warner commented 2016-06-28 18:20:37 +00:00
Author
Owner

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders
tahoe-lafs modified the milestone from 1.12.0 to 1.13.0 2016-06-28 18:20:37 +00:00
exarkun commented 2020-01-09 18:55:48 +00:00
Author
Owner

Some Windows packaging would be great. The extended support window for Windows 7 is closing in a handful of days and Windows 8 is a train wreck that no one should use (supporting evidence: see if you can figure out when Windows 8 support ended or will end).

Also, there is a PyInstaller spec for Tahoe-LAFS in the repo and tested on CI. So, in fact, there apparently is some Windows packaging.

Therefore, considering this fixed.

Some Windows packaging would be great. The extended support window for Windows 7 is closing in a handful of days and Windows 8 is a train wreck that no one should use (supporting evidence: see if you can figure out when Windows 8 support ended or will end). Also, there *is* a [PyInstaller](wiki/PyInstaller) spec for Tahoe-LAFS [in the repo](https://github.com/tahoe-lafs/tahoe-lafs/blob/e1acacdae26722960461e250366be84a66d83f67/pyinstaller.spec) and [tested on CI](https://github.com/tahoe-lafs/tahoe-lafs/blob/e1acacdae26722960461e250366be84a66d83f67/.circleci/config.yml#L93-L116). So, in fact, there apparently is some Windows packaging. Therefore, considering this fixed.
tahoe-lafs added the
fixed
label 2020-01-09 18:55:48 +00:00
exarkun closed this issue 2020-01-09 18:55:48 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#195
No description provided.