Skip to content

Commit 4c474f9

Browse files
author
Paul Baker
committed
Improving readme.
1 parent 28cdc0f commit 4c474f9

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

README.md

+5-11
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,15 @@
11
# git-openssl-shellscript
22
Shellscript to compile git with OpenSSL
33

4-
## git-openssl-experimental.sh
4+
## For both scripts
5+
Compiling and running the tests to ensure functionailty are long. To save time, pass the ```-skiptests``` argument to the script you run. Tests will be skipped and the script will procede without them.
6+
7+
### git-openssl-experimental.sh
58
This script is better than the other one, in that it pulls git source code directly from it's head repository and then compiles it. This gives you the benefit of using the most recent stable version which solves a lot of issues, in and of itself. It also compiles git-credential-gnome-keyring so credentials are using the keyring by default. It adds convienience to not having to retype passwords and security by not storing them in cleartext.
69

710
That being said, it is experimental. Use at your own peril. If things go south, just purge all git and re-install or use the regular shellscript
811

9-
## git-openssl.sh
12+
### git-openssl.sh
1013

1114
There are at times when you need to use git with https instead of ssh (behind firewalls where ssh is not allowed but https is, for instance). There is a gnutls issue that prevents communication with some https behind such firewalls or unusual proxy configurations, etc. You will typically see an error such as this:
1215
```
@@ -15,12 +18,3 @@ fatal: unable to access 'http://you@path.to/arbitrary/repository/git-openssl-she
1518
The only way to resolve this is by re-compiling git with `openssl` instead of `gnutls`.
1619

1720
This shellscript does that by downloading the source for git, switching it to `openssl` and and then building it. If you are using a managed version of git (eg: through ubuntu's package manager) you will have to re-run the script every time you recieve an updated version of git because the managed version will overwrite your compiled version.
18-
19-
Compiling and running the tests to ensure functionailty are long. To save time, uncomment
20-
```
21-
#sed -i -- '/TEST\s*=\s*test/d' ./debian/rules
22-
```
23-
so it looks like this
24-
```
25-
sed -i -- '/TEST\s*=\s*test/d' ./debian/rules
26-
```

0 commit comments

Comments
 (0)