Skip to content
Gnome SSH Tunnel Manager - Gtk3 Edition
Branch: master
Clone or download
dallenwilson Update README.md
Added link to the AUR package page. Thanks go to Hrotkó Gábor <hrotko.gabor@gmail.com> for notifying the AUR maintainer and getting it updated there.
Latest commit b5289dd May 6, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
gAskpass gAskpass: Treat arguement as label Apr 11, 2019
pixmaps Reverted last two commits; Found simpler way to ensure menu icon works. Mar 7, 2019
po Added files to translation list. Jan 22, 2019
src Version bump for next release. Apr 18, 2019
.gitignore
AUTHORS
COPYING Fixed files-oops. Jan 14, 2019
ChangeLog Gtk2 -> Gtk3 migration. Jan 14, 2019
INSTALL Gtk2 -> Gtk3 migration. Jan 14, 2019
Makefile.am
NEWS Fixed files-oops. Jan 14, 2019
README Updated README; Version bump 1.3.0->1.3.1. Mar 7, 2019
README.md
autogen.sh
configure.ac Version bump for next release. Apr 18, 2019
gstm.anjuta Gtk2 -> Gtk3 migration. Jan 14, 2019
gstm.desktop Corrected desktop menu icon location Mar 5, 2019
intltool-extract.in Gtk2 -> Gtk3 migration. Jan 14, 2019
intltool-merge.in Gtk2 -> Gtk3 migration. Jan 14, 2019
intltool-update.in Gtk2 -> Gtk3 migration. Jan 14, 2019

README.md

gstm - Gnome SSH Tunnel Manager

Gtk3 Edition

This is a Gtk3 port of gstm, based on v1.2 available at: https://sourceforge.net/projects/gstm/

Dependencies on deprecated libgnome libraries have also been removed.

Packaging & Releases
Building from Source

If you're building from a release tarball, you'll need pkg-config, gtk3, libxml2, and intltool along with their associated dev packages. The configure script and makefiles are included in the tarball.

Building direct from the git repo, you'll need the above as well as autoconf (>=2.69) and automake. There is a bash script (autogen.sh) to handle the autoconf/automake work and generate the configure script and various makefiles. Run it, then the usual ./configure && make.

Bugs and Issues

Bugs can be reported using GitHub's Issues tab. Before opening a new issue, try reproducing the problem after building the lastest source from the master branch. Also, take a look through the closed issues to see if it's been reported before. This is doubly important if you're using packages from the ppa; Those tend to lag a bit behind.

You can’t perform that action at this time.