There are probably more clever ways to do this, but as a quick and dirty hack I find this useful for finding out which methods are being, or could potentially be, called on my object:
I mentioned connect.c for SOCKS proxy connections. Compiling it on Solaris 10 is relatively straightforward but you need to define INADDR_NONE as it’s not present in the system headers.
You also need to link it with libnsl, libsocket and libresolv.
I’m working with an application which requires Trang to convert RELAX NG schema files. Trang itself is quite old code and this seems to present problems on newer distributions - all sorts of problems getting it to run under GCJ in particular.
While there are probably speed advantages in going the GCJ route, I’m more interested in just getting it working - the schema files only need converting once so speed isn’t really an issue here.
I cheated and just used the JDK and a shell script wrapper. If you just need it to work too, here’s how I did it.
Install JDK
This is obviously different for every platform, but in this case it’s on Ubuntu and is as simple as:
sudo aptitude install sun-java5-jdk
Fetch Trang
You need the original Java zip file, not the GCJ version.
From this you need to extract the jar file:
Install Trang
I placed mine in /usr/local/trang but it doesn’t really matter where it goes.
Create a wrapper shell script
The shell script just invokes java on the Trang jar file with the supplied arguments. Create the file /usr/local/bin/trang in your favourite editor:
And then make the script executable:
Test it
Assuming the script is in your PATH, you should now be able to use it as normal (albeit slowly - the startup time hurts a bit!)
I use Git both at home and at work; at home I’ve got a direct connection but at work I must connect through a SOCKS proxy for external access.
Although Git supports proxy configuration, it’s irritating to have to change this all the time depending on my location. Setting the environment variable GIT_PROXY_COMMAND overrides whatever proxy configuration already exists - this is all we need to get git:// repositories to work. To get Git-over-SSH connections to work, which you probably want for push operations, you’ll also need to set up GIT_SSH.
I’ve created some simple shell scripts to help. The first is a simple wrapper for connect.c (which you may need to compile, of course).
The second is another simple wrapper for SSH through a SOCKS proxy:
Lastly, I have a script I source when at work to set the environment variables for me:
And I’ve put an alias in my .bash_profile to help me remember to source it instead of running it:
Now when I use Git at home, it just works without having to remove any proxy config, and when I use it at work I just type work in my shell and it works there too…