separate HotSSH version

2 views
Skip to first unread message

Colin Walters

unread,
May 9, 2008, 5:49:41 PM5/9/08
to Hotwire Shell
Hi,

I blogged about a new version of HotSSH, the previously-included Unix-
only SSH client:

http://cgwalters.livejournal.com/16940.html

As I mentioned my plan is to eventually migrate it out of Hotwire and
into GNOME proper, since it's unlikely to become crossplatform anytime
soon.

If you're a Hotwire packager for a distribution, this is now a
separate source distribution so you'll want a new binary package too.
Let me know if you run into any trouble!

Hamish

unread,
May 11, 2008, 6:27:47 PM5/11/08
to Hotwire Shell
Just done an svn update and ssh no longer works from within hotwire.
hotapps/hotssh/ is now empty.

I've tried a couple of things and have failed to get ssh working so
far. Do I need to update some paths? import statements? Should
hotssh be checked out to be in the hotwire directory structure?

Colin Walters

unread,
May 16, 2008, 8:18:14 PM5/16/08
to Hotwire Shell
Hi, basically hotwire-ssh is a separate (but related) project now. My
short/medium term plan is to get it into GNOME by default. Hotwire
Shell is going to be a running prototype/experiment for the near
future.

So you'll need to install it separately. It should work to just
unpack it and add /path/to/hotwire-ssh/bin to your PATH; but the ideal
would be for it to see it shipped by GNOME/distributions. I need to
get some time to work on making that happen.

Hamish

unread,
May 20, 2008, 1:03:45 PM5/20/08
to Hotwire Shell
> So you'll need to install it separately.  It should work to just
> unpack it and add /path/to/hotwire-ssh/bin to your PATH;

For anyone else wondering, this is what I did to add the path. I
created ~/.hotwire/plugins/myenv.py and in it I put

import os
os.environ['PATH'] = '/path/to/hotwire-ssh/bin:' + os.environ['PATH']

For more details about this, see http://code.google.com/p/hotwire-shell/wiki/ExtendingHotwire
Reply all
Reply to author
Forward
0 new messages