From 7cabb6c1b337cb8b7fe3ada3926ec0bf42d055d7 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:09:45 +0200 Subject: [PATCH 01/14] Change ELusive reference to reference to SGML+DOM stuff ref. Such a change takes one _really_ bored ELinks hacker in a night bus (and a distributed VCS, woo-hoo). Yawn. --- TODO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TODO b/TODO index 75c1f787c..93050f622 100644 --- a/TODO +++ b/TODO @@ -7,7 +7,7 @@ What yet needs to take its way to Bugzilla: Some rules for sane handling of texinfo documentation - Rewrite HTML parser (see ELusive, src/elusive/TODO) + Rewrite HTML parser (see the SGML+DOM stuff, src/document/sgml) Reorganization of user interface (nothing particular at all, just an uncertain feel that it could be better and bear a look of some UI designer ;) From a529ed444b240e5c4f92da307e376a45285ed158 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:16:24 +0200 Subject: [PATCH 02/14] A feeble attempt to fix the atrocious grammar in doc/README. --- doc/README | 38 ++++++++++++++++++++------------------ 1 file changed, 20 insertions(+), 18 deletions(-) diff --git a/doc/README b/doc/README index f50b40570..639a180d1 100644 --- a/doc/README +++ b/doc/README @@ -1,23 +1,24 @@ Overview of the ELinks documentation -There is only limited documentation available for ELinks, sorry. It basically -consists of the documents in this directory and the features.conf, README and -INSTALL files in the project's root directory. +There is only limited documentation available for ELinks so far, sorry. It +basically consists of the documents in this directory and the features.conf, +README and INSTALL files in the project's root directory. -The files you will find in this directory are the man pages living in the man/ +The files you will find in this directory are manpages living in the man/ directory and a bunch of .html and especially .txt (wait, you expect HTML -browser to carry its documentation around in HTML?). The index.txt file -contains the table of contents listing all these files. +browser to carry its documentation around in HTML?) documents. The index.txt +file contains the table of contents which should help you navigating between +the files. Tools ----- -The manual is written in asciidoc. However you will also need xmlto to process -docbook XML generated by asciidoc into manpages and the html-chunked manual. If -you want to translate .pod files you need pod2html. +The manual is written in asciidoc, however you will also need xmlto to process +docbook XML generated by asciidoc into manpages and the html-chunked manual. +If you want to translate .pod files you need pod2html. -All these tools are checked by configure so that to successfully build all -possible documentation (with the tools available on the system) run +All these tools are checked by configure, thus to successfully build all the +possible documentation (with the tools available on the system), just run $ make all-docs @@ -26,16 +27,17 @@ in the doc/ directory. Contributing ------------ -Contributions are very warmly welcomed. Wether it be fixing of typos or bad -grammar, rewritings or new material. All info relevant to ELinks usage can be -included in the manual. Including FAQ material, tips and cheats ;) +Contributions are very warmly welcomed, whether it is fixing typos or bad +grammar, rewritings or new material. Any information relevant to ELinks usage +can be included in the manual, including FAQ material, tips and cheats ;) -There is no strict codingstyle. But please don't limit your use of whitespace +There is no strict codingstyle, but please don't limit your use of whitespaces and take a look at the style used in the current documents to get ideas of what is reasonable. -Contributions should be sent to Jonas Fonseca . If your changing -something in an existing document please read about how to make unified patches -in the Patches section of the doc/hacking.txt file. +Contributions should be sent to Jonas Fonseca or to the +ELinks mailing list. If you are changing something in an existing document, +please read about how to make unified patches in the Patches section of the +doc/hacking.txt file. $Id: README,v 1.14 2005/05/24 19:05:14 jonas Exp $ From fa366e9fdbb0c5327849fc140292d7adbbd278c8 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:16:50 +0200 Subject: [PATCH 03/14] Remove the ref. to now non-existing doc/book/TODO. --- TODO | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TODO b/TODO index 93050f622..f9e18a90d 100644 --- a/TODO +++ b/TODO @@ -15,7 +15,7 @@ uncertain feel that it could be better and bear a look of some UI designer ;) General goals: - Write some more documentation.. docs, a lot of docs! (see doc/book/TODO) + Write some more documentation.. docs, a lot of docs! General code cleanup From b768220dbbd928c8d7b59d61e7501fe7884e4aca Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:20:17 +0200 Subject: [PATCH 04/14] Reference http://elinks.cz/ instead of http://elinks.or.cz/ Let's actually let the world know about the elinks.cz domain so generously donated to us. --- SITES | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/SITES b/SITES index da2c970cd..46dc2bc67 100644 --- a/SITES +++ b/SITES @@ -1,5 +1,5 @@ Homepage: - http://elinks.or.cz/ + http://elinks.cz/ DEBs: http://packages.debian.org/testing/web/elinks.html @@ -14,11 +14,11 @@ Cygwin binaries: http://www.pervalidus.net/cygwin/links/ GIT root: - http://elinks.or.cz/elinks.git + http://elinks.cz/elinks.git git+ssh://pasky.or.cz/srv/git/elinks.git (master, DEPRECATED) Mailing list: - http://elinks.or.cz/community.html#mailinglist + http://elinks.cz/community.html#mailinglist elinks-users@linuxfromscratch.org (user discussion, announcements) elinks-dev@linuxfromscratch.org (weird development and sorcery talks) listar@linuxfromscratch.org (Subject: subscribe elinks-users) From 104969d00c7f3a1812ac9333ba115ca3cb8e5414 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:21:46 +0200 Subject: [PATCH 05/14] The list of recent changes is available thru gitweb --- NEWS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 39b8be00f..4d20227dc 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,5 @@ -See ChangeLog for recent changes, bugfixes and new features. +You can see the complete list of recent changes, bugfixes and new features +in the gitweb interface. See the ChangeLog file for details. ELinks now: From 9e61cbfb499ee197b74683fecf779132d376abe6 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:24:04 +0200 Subject: [PATCH 06/14] NEWS items aren't complete sentences, so remove trailing fullstops and stuff --- NEWS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/NEWS b/NEWS index 4d20227dc..7469eaaec 100644 --- a/NEWS +++ b/NEWS @@ -3,13 +3,13 @@ in the gitweb interface. See the ChangeLog file for details. ELinks now: -* support for Lua 4.x was dropped, we only support Lua 5.x now. +* support for Lua 4.x was dropped, we only support Lua 5.x now * Python scripting back-end (experimental) * 88 colors support * external editor is configurable at run-time -* Default URI-rewrite rule, used when no other rules match but the string +* default URI-rewrite rule, used when no other rules match but the string that was entered in the Go to URL box does not resemble a URI -* Support prefixes for add-bookmark-link, document-info, goto-url-current-link, +* support prefixes for add-bookmark-link, document-info, goto-url-current-link, history-move-back, and history-move-forward * BitTorrent protocol (experimental) * FSP protocol via a CGI script (see contrib/cgi/README.FSP) (experimental) @@ -18,7 +18,7 @@ ELinks now: ELinks 0.10.4: * explicit keyboard accelerators were defined for buttons in dialogue boxes - and are now highlighted. + and are now highlighted ELinks 0.10.2: From eb226549110ee7a957bec19d97ab367d27988b40 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:26:09 +0200 Subject: [PATCH 07/14] Me Og, Og correct English not to look like Og speaking. --- contrib/cgi/README.FSP | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/contrib/cgi/README.FSP b/contrib/cgi/README.FSP index f69485861..537befc35 100644 --- a/contrib/cgi/README.FSP +++ b/contrib/cgi/README.FSP @@ -1,8 +1,8 @@ -To use this cgi script: +To use this CGI script you need to build fspcgi and copy the executable +to your cgi directory. In ELinks, you can then use this URL: -Build fspcgi, copy executable to your cgi directory. -Usage: -file:///"path_to_fspcgi"?host:port/path_to_file_or_directory + file:///"path_to_fspcgi"?host:port/path_to_file_or_directory +You can find more info about the FSP protocol at -More info about FSP protocol you find on http://fsp.sourceforge.net/. + http://fsp.sourceforge.net/ From 9325c52067db342d1360cbbbdf0cb2087d0a9a09 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:33:36 +0200 Subject: [PATCH 08/14] Clarify the GPL upgrades policy a bit, and propose an addition The proposed addition is that if the current ELinks maintainer likes GPLv3, he might have the right to relicence all the default GPLv2-only contributions to GPLv3. Please state your opinions etc. --- COPYING | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/COPYING b/COPYING index 7f981ed87..7d2a85a4c 100644 --- a/COPYING +++ b/COPYING @@ -1,6 +1,15 @@ Note that the only valid version of the GPL as far as ELinks is concerned is _this_ particular version of the license (ie v2, not v2.2 -or v3.x or whatever), unless explicitly otherwise stated. +or v3.x or whatever), unless explicitly stated otherwise. That is at +least the policy for all pasky's contributions and the default - if you +want different policy for your patches, the best way to state it is by +a patch for your AUTHORS entry. + +If pasky likes GPLv3, he might relicence his contributions for GPLv3 +as well. The default policy should probably be that you trust pasky, +Jonas, or the current maintainer of the day to do the right thing (much +like it is in the Linux kernel). But this needs to be yet worked out +and agreed upon. ----------------------------------------------------------------------- From 183916d9eec89e523190d7e619c1416d514da1ad Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:40:37 +0200 Subject: [PATCH 09/14] Retouch the history section (does it really belong here?). Also various reformatting. --- README | 58 +++++++++++++++++++++++++++++++++------------------------- 1 file changed, 33 insertions(+), 25 deletions(-) diff --git a/README b/README index 31366b651..aad351610 100644 --- a/README +++ b/README @@ -6,10 +6,13 @@ ELinks is an advanced and well-established feature-rich text mode web customizable and can be extended via scripts. It is very portable and runs on a variety of platforms. -The ELinks official website is available at http://elinks.or.cz/. -Please see the SITES file for mirrors or other recommended sites. -If you want to install ELinks on your computer, see the -INSTALL file for further instructions. +The ELinks official website is available at + + http://elinks.or.cz/ + +Please see the SITES file for mirrors or other recommended sites. If you +want to install ELinks on your computer, see the INSTALL file for further +instructions. A good start point is documentation files available in doc/, especially the file named index.txt. @@ -24,35 +27,40 @@ document. If you want to add a new language or update the translation for an existing one, please read po/README document. -If you want to write some documentation, well you're welcomed ;) +If you want to write some documentation, well, you're welcome! ;) -History -~~~~~~~ +Historical notes +~~~~~~~~~~~~~~~~ -Initially, ELinks was a development version of Links (Lynx-like text WWW browser), -with more liberal features policy and development style. - -Its purpose was to provide an alternative to Links, and to test and tune various -new features, but still provide good rock-solid releases inside stable branches. -If you are more interested, you can examine the Links website at -http://links.sf.net/. +Initially, ELinks was a development version of Links (Lynx-like text WWW +browser), with more liberal features policy and development style. Its purpose +was to provide an alternative to Links, and to test and tune various new +features, but still provide good rock-solid releases inside stable branches. Why not contribute to Links instead? Well, first I made a bunch of patches for -the original Links, but a significant number of them got refused because -Mikulas did not like them, as he just wouldn't have any use for them himself. -He wants to keep Links with a relatively closed feature set and merge only new -features which he himself needs. It has advantages that the tree is very narrow -and the code is small and contains very little bloat. ELinks, on the contrary, -aims to provide a full-featured web browser, superior to both lynx and w3m and -with the possibilities of Konqueror and similar browsers. However, to prevent -drastic bloating of the code, the development is driven in the course of -modularization and separation of add-on modules (like cookies, bookmarks, ssl, -lua etc). +the original Links, but Mikulas wasn't around to integrate them, so I started +releasing my fork. When he came back, a significant number of them got refused +because Mikulas did not like them, as he just wouldn't have any use for them +himself. He wants to keep Links with a relatively closed feature set and merge +only new features which he himself needs. It has advantages that the tree is +very narrow and the code is small and contains very little bloat. -For more about ELinks history, see http://elinks.or.cz/history.html +ELinks, on the contrary, aims to provide a full-featured web browser, superior +to both lynx and w3m and with the power (but not slowness and memory usage) of +Mozilla, Konqueror and similar browsers. However, to prevent drastic bloating +of the code, the development is driven in the course of modularization and +separation of add-on modules (like cookies, bookmarks, ssl, scripting etc). +For more details about ELinks history, please see + + http://elinks.or.cz/history.html + +If you are more interested in the history and various Links clones and versions, +you can examine the website at + + http://links.sf.net/ From 86655626b51ba1314ea0cf0bf82fd0a9b964a858 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:48:21 +0200 Subject: [PATCH 10/14] General retouching, style and grammar fixes etc. --- INSTALL | 45 +++++++++++++++++++++++---------------------- 1 file changed, 23 insertions(+), 22 deletions(-) diff --git a/INSTALL b/INSTALL index 36d35987f..9f879d084 100644 --- a/INSTALL +++ b/INSTALL @@ -6,8 +6,8 @@ Elinks installation guidelines ./configure && make && make install Check out the bottom of this file if you're upgrading from Links or an older -ELinks! And be sure to look at doc/ecmascript.txt if you want ECMAScript -(that's JavaScript) support. +ELinks! And be sure to look at doc/ecmascript.txt if you want (experimental) +ECMAScript (that's JavaScript) support. ########## @@ -40,15 +40,15 @@ snapshot - you don't need to do this there. ########## - If you want to compile elinks, first check the directory named contrib/, it + If you want to compile ELinks, first check the directory named contrib/, it may contain patches that are of use to you. If you're interested in any of them, try to apply them by doing (for each one): $ patch -p0 < contrib/that-patch - They may not apply - I don't update patches in contrib/ regularly - if you -want, feel free to go ahead and update the patch for the current tree and send -me the newer version. + They may not apply, since I don't update patches in contrib/ regularly - if +you want, feel free to go ahead and update the patch for the current tree and +submit the newer version. Usually, even after strip, the ELinks binary can grow a lot these days; I plan on spawning various external files optionally, containing boring stuff like @@ -84,7 +84,7 @@ recommended for users to give a strong preference to OpenSSL whenever possible. Good luck! - The basic compilation looks like: + The compilation itself looks like: Unix - just doing: @@ -93,15 +93,15 @@ recommended for users to give a strong preference to OpenSSL whenever possible. should be enough. However, in some FreeBSD 3 distributions you have to set CFLAGS=-aout before running ./configure. Also, you may want to - adjust some compile-time options through ./configure - do - ./configure --help and it'll print out a list of them. You can more - finely control what's going to be included in the binary in the - features.conf file, and some really detailed tuning can be performed in - the src/setup.h. + adjust some (well, plenty of) compile-time options through ./configure + - do ./configure --help and it'll print out a list of them. You can + finetune what's going to be included in the binary in the features.conf + file, and some really detailed tuning can be performed in src/setup.h. - Also, a nice idea is to compile ELinks outside of the source tree. - Make another directory and run path_to_source_tree/configure from it. - Typically, it looks like: + Also, a nice idea is to compile ELinks outside of the source tree (note + that this might not quite work right now, but we're working on fixing + it). Make another directory and run path_to_source_tree/configure from + it. Typically, it looks like: $ mkdir ../elinks-build $ cd ../elinks-build @@ -123,7 +123,7 @@ recommended for users to give a strong preference to OpenSSL whenever possible. SET MAKE=d:/prg/emx/bin/make.exe SET EMXOPT=-h100 - Dos, Windows - port it by yourself. + DOS, Windows - port it by yourself. ########## @@ -141,10 +141,11 @@ recommended for users to give a strong preference to OpenSSL whenever possible. before you run links. Now, check the contrib/ directory again. There may be some useful config -file examples there, along with a few support tools and some Lua scripts - you -probably want them ;) so just copy the hooks.lua to ~/.elinks, and edit the +file examples there, along with few support tools and some Lua scripts - you +probably want them ;) so just copy hooks.lua to ~/.elinks, and edit the configuration part - it adds various functionality to ELinks, like -decompression of gzipped files or user-defined protocols. +decompression of gzipped files or HTML code rewriting for ELinks-unfriendly +websites. ########## @@ -156,11 +157,11 @@ the old (E)Links, so you probably want to make a links symlink pointing to elinks. Then, note that configuration files were moved from /etc to /etc/elinks and -from ~/.links to ~/.elinks, because the name and format of parts of them were +from ~/.links to ~/.elinks, because the name and format of some of them was changed: links.cfg became elinks.conf and you need to convert it with -contrib/conv/conf-links2elinks.pl; html.cfg was merged into elinks.conf +contrib/conv/conf-links2elinks.pl; html.cfg was merged into elinks.conf. bookmarks are still bookmarks, but you need to convert it with old_to_new_bookmarks.sh. @@ -169,7 +170,7 @@ old_to_new_bookmarks.sh. history became globhist and the format is the same. - cookies are still cookies, but you need to convert it with tr " " "\t" + cookies are still cookies, but you need to convert it with tr " " "\t". ########## From d68fd7aa4bce764df3132fd857680737379e0b36 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:51:35 +0200 Subject: [PATCH 11/14] Remove some ancient reducing-binary-size stuff Instead refer to doc/small.txt. --- INSTALL | 21 +++++---------------- 1 file changed, 5 insertions(+), 16 deletions(-) diff --git a/INSTALL b/INSTALL index 9f879d084..1b361c35c 100644 --- a/INSTALL +++ b/INSTALL @@ -50,22 +50,11 @@ $ patch -p0 < contrib/that-patch you want, feel free to go ahead and update the patch for the current tree and submit the newer version. - Usually, even after strip, the ELinks binary can grow a lot these days; I plan -on spawning various external files optionally, containing boring stuff like -various translations etc; later, even DSO modules may come, etc. But even -nowadays, you can reduce the resulting binary size by throwing out stuff you -don't like. First, if you want better performance and a smaller binary, don't -compile it with debug. It won't hurt if you do, though, and ELinks will tell -you about any memory leaks, incorrect memory manipulation etc, which may be -helpful to us if you report it. Next, disable any optional features you are not -going to use, they can make the resulting binary smaller (although it'll probably -have no non-marginal performance impact) - especially go through the -features.conf file in the project root directory. Also, you may try to override -the build system to build a dynamically linked binary, which can be a lot -smaller as well. Lastly, you can go to the Unicode/ and intl/ directories, then -edit index.txt and remove any codepages or translations you don't like; -especially for translations, it can significantly reduce the resulting binary -size as well. + Usually, even after strip, the ELinks binary can measure a lot, but you can +radically reduce the resulting binary size by throwing out stuff you don't like. +Detailed discussion of reducing the executable size can be found in + + doc/small.txt !BEWARE! If you _distribute_ a binary of ELinks with OpenSSL linked to it, and the OpenSSL library is not part of your base system, you are VIOLATING THE From 8623d1ce8c18e079574a88cb18a7de09a1da2557 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:53:27 +0200 Subject: [PATCH 12/14] Mention that the GNUTLS SSL support is 1.2+ Suggested by Miernik. --- configure.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.in b/configure.in index d732b48b0..5037c5db5 100644 --- a/configure.in +++ b/configure.in @@ -786,9 +786,9 @@ disable_openssl="" disable_gnutls="" enable_gnutls="" -AC_ARG_WITH(gnutls, [ --without-gnutls disable GNUTLS SSL support], +AC_ARG_WITH(gnutls, [ --without-gnutls disable GNUTLS (1.2+) SSL support], [if test "$with_gnutls" = no; then disable_gnutls=yes; fi]) -AC_ARG_WITH(gnutls, [ --with-gnutls[=DIR] enable GNUTLS SSL support], +AC_ARG_WITH(gnutls, [ --with-gnutls[=DIR] enable GNUTLS (1.2+) SSL support], [if test "$with_gnutls" != no; then enable_gnutls=yes; fi]) gnutls_withval="$withval" From 5f0533617048433db52cd9823c138b7a36f56d07 Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 03:53:50 +0200 Subject: [PATCH 13/14] Move bits around to more appropriate places --- INSTALL | 45 ++++++++++++++++++++++----------------------- 1 file changed, 22 insertions(+), 23 deletions(-) diff --git a/INSTALL b/INSTALL index 1b361c35c..afc41fd59 100644 --- a/INSTALL +++ b/INSTALL @@ -50,29 +50,6 @@ $ patch -p0 < contrib/that-patch you want, feel free to go ahead and update the patch for the current tree and submit the newer version. - Usually, even after strip, the ELinks binary can measure a lot, but you can -radically reduce the resulting binary size by throwing out stuff you don't like. -Detailed discussion of reducing the executable size can be found in - - doc/small.txt - - !BEWARE! If you _distribute_ a binary of ELinks with OpenSSL linked to it, -and the OpenSSL library is not part of your base system, you are VIOLATING THE -GPL (although I believe that for this absurd case no ELinks copyright holder -will sue you, and it's not a problem for the OpenSSL people as well, as they -have explicitly told me). So, people who are making ELinks binaries for systems -with no OpenSSL in the base system and who decided to link OpenSSL against the -ELinks binary may wish NOT to publish or distribute such a binary, as it's -breaking GPL 2(b), if they like to have everything legally perfect (like Debian -people ;). As a semi-solution to this for those people, GNUTLS support was -introduced; if you want to distribute ELinks binaries with HTTPS support, -compile ELinks with the --with-gnutls configure option (assuming that you have -GNUTLS 0.5.0 or later [tested with 0.5.4] installed). However, as GNUTLS is not -yet 100% stable and its support in ELinks is not so well tested yet, it's -recommended for users to give a strong preference to OpenSSL whenever possible. - - Good luck! - The compilation itself looks like: Unix - just doing: @@ -114,6 +91,12 @@ recommended for users to give a strong preference to OpenSSL whenever possible. DOS, Windows - port it by yourself. + Usually, even after strip, the ELinks binary can measure a lot, but you can +radically reduce the resulting binary size by throwing out stuff you don't like. +Detailed discussion of reducing the executable size can be found in + + doc/small.txt + ########## @@ -137,6 +120,22 @@ decompression of gzipped files or HTML code rewriting for ELinks-unfriendly websites. + !BEWARE! If you _distribute_ a binary of ELinks with OpenSSL linked to it, +and the OpenSSL library is not part of your base system, you are VIOLATING THE +GPL (although I believe that for this absurd case no ELinks copyright holder +will sue you, and it's not a problem for the OpenSSL people as well, as they +have explicitly told me). So, people who are making ELinks binaries for systems +with no OpenSSL in the base system and who decided to link OpenSSL against the +ELinks binary may wish NOT to publish or distribute such a binary, as it's +breaking GPL 2(b), if they like to have everything legally perfect (like Debian +people ;). As a semi-solution to this for those people, GNUTLS support was +introduced; if you want to distribute ELinks binaries with HTTPS support, +compile ELinks with the --with-gnutls configure option (assuming that you have +GNUTLS 0.5.0 or later [tested with 0.5.4] installed). However, as GNUTLS is not +yet 100% stable and its support in ELinks is not so well tested yet, it's +recommended for users to give a strong preference to OpenSSL whenever possible. + + ########## If you're upgrading from Links or older ELinks (0.4pre7 or older), you will From 744a87cea25f8b94a646ff964fa476d3ab18ef4f Mon Sep 17 00:00:00 2001 From: Petr Baudis Date: Sat, 17 Sep 2005 04:01:08 +0200 Subject: [PATCH 14/14] Significantly retouch the OpenSSL vs. GNUTLS tractate. --- INSTALL | 36 ++++++++++++++++++++++-------------- 1 file changed, 22 insertions(+), 14 deletions(-) diff --git a/INSTALL b/INSTALL index afc41fd59..778a6fa39 100644 --- a/INSTALL +++ b/INSTALL @@ -120,20 +120,28 @@ decompression of gzipped files or HTML code rewriting for ELinks-unfriendly websites. - !BEWARE! If you _distribute_ a binary of ELinks with OpenSSL linked to it, -and the OpenSSL library is not part of your base system, you are VIOLATING THE -GPL (although I believe that for this absurd case no ELinks copyright holder -will sue you, and it's not a problem for the OpenSSL people as well, as they -have explicitly told me). So, people who are making ELinks binaries for systems -with no OpenSSL in the base system and who decided to link OpenSSL against the -ELinks binary may wish NOT to publish or distribute such a binary, as it's -breaking GPL 2(b), if they like to have everything legally perfect (like Debian -people ;). As a semi-solution to this for those people, GNUTLS support was -introduced; if you want to distribute ELinks binaries with HTTPS support, -compile ELinks with the --with-gnutls configure option (assuming that you have -GNUTLS 0.5.0 or later [tested with 0.5.4] installed). However, as GNUTLS is not -yet 100% stable and its support in ELinks is not so well tested yet, it's -recommended for users to give a strong preference to OpenSSL whenever possible. + !BEWARE! If you _distribute_ an ELinks executable linked with OpenSSL and +the OpenSSL library is not part of your base system, you are VIOLATING THE GPL. +I honestly believe that for this absurd case no ELinks copyright holder will +sue you, and it's not a problem for the OpenSSL people as well, as they have +explicitly told me, but you might stay on the safe side. + + So, people who are making ELinks binaries for systems with no OpenSSL in the +base system and who decided to link OpenSSL against the ELinks binary may wish +NOT to publish or distribute such an executable, as it's breaking GPL 2(b), if +they like to have everything legally perfect (like the Debian people ;-). + + As a semi-solution to this problem, GNUTLS support was introduced; if you want +to distribute ELinks executables with HTTPS support, compile ELinks with the +--with-gnutls configure option (assuming that you have GNUTLS 1.2.0 installed; +we can't say about later versions since GNUTLS people seem to have strange taste +wrt. backwards compatibility). + + HOWEVER, beware that GNUTLS support in ELinks is not so well tested as +OpenSSL, and shall be probably still considered experimental. Therfore, it's +recommended to the users to give OpenSSL strong preference whenever possible. +(Just to show the GNU ideologists how silly can they sometimes be, if not +anything else. ;-) ##########