Opened at 2010-06-08T18:29:39Z
Last modified at 2011-02-20T06:13:49Z
#1074 closed defect
get rid of tahoe.exe launcher — at Version 1
Reported by: | zooko | Owned by: | davidsarah |
---|---|---|---|
Priority: | major | Milestone: | 1.8β |
Component: | packaging | Version: | 1.6.1 |
Keywords: | windows win64 setuptools unicode reviewed | Cc: | sneves |
Launchpad Bug: |
Description (last modified by davidsarah)
There is a binary (cli.exe) in the Tahoe-LAFS source tree under revision control. It is built from launcher.c in zetuptoolz:
http://tahoe-lafs.org/trac/zetuptoolz/browser/launcher.c
source:setup.py copies it to bin\tahoe.exe when building.
There are several reasons to get rid of this launcher:
- it mangles any non-ASCII arguments, preventing us from fixing #565 on Windows;
- it adds a small amount of overhead to running CLI commands;
- it's unnecessary complexity;
- it isn't in the spirit of open source to have a binary that is not compiled from source as part of our build process -- getting rid of it fixes this without complicating the build or requiring a C compiler;
- a Python script called tahoe.py can be run just fine on Windows as tahoe, provided that the PATHEXT environment variable includes ".py".
Change History (2)
comment:1 Changed at 2010-06-08T18:56:09Z by davidsarah
- Description modified (diff)
- Owner changed from somebody to davidsarah
- Status changed from new to assigned
- Summary changed from there is a binary (cli.exe) in the Tahoe-LAFS source tree under revision control to get rid of tahoe.exe launcher
Changed at 2010-06-08T23:29:51Z by davidsarah
Note: See
TracTickets for help on using
tickets.
Attaching my work-in-progress for Unicode argument support on Windows and removal of tahoe.exe, so that it doesn't get lost.