aboutsummaryrefslogtreecommitdiff
path: root/gnurl.html.j2
diff options
context:
space:
mode:
Diffstat (limited to 'gnurl.html.j2')
-rw-r--r--gnurl.html.j230
1 files changed, 12 insertions, 18 deletions
diff --git a/gnurl.html.j2 b/gnurl.html.j2
index 746567e7..32947239 100644
--- a/gnurl.html.j2
+++ b/gnurl.html.j2
@@ -2,24 +2,27 @@
2{% block body_content %} 2{% block body_content %}
3<div class="container-fluid"> 3<div class="container-fluid">
4 <div class="container text-center"> 4 <div class="container text-center">
5 <h1>{{ _("gnurl / libgnurl") }}</h1> 5 <h1>{{ _("gnurl (libgnurl)") }}</h1>
6 <p> 6 <p>
7 {% trans %} 7 {% trans %}
8 libgnurl is a micro fork of libcurl, which is mostly for GNUnet 8 libgnurl is a micro fork of libcurl. The goal of libgnurl
9 but it might 9 is to support only HTTP and HTTPS (and only HTTP 1.x) with
10 be usable for others, hence we're releasing the code 10 a single crypto backend (GnuTLS) to ensure a small footprint
11 to the general public. libgnurl is released under the same 11 and uniform experience for developers regardless of how
12 libcurl was compiled.<br>
13 Our main usecase is for GNUnet, but it might be usable for
14 others, hence we're releasing the code
15 to the general public.<br>
16 libgnurl is released under the same
12 license as libcurl. Please read the README for instructions, as you 17 license as libcurl. Please read the README for instructions, as you
13 must supply the correct options to configure to get a proper build of 18 must supply the correct options to configure to get a proper build of
14 libgnurl. 19 libgnurl.
15 In the following, I will explain the motiviations behind
16 this fork.
17 {% endtrans %} 20 {% endtrans %}
18 </p> 21 </p>
19 <h3>{{_("Motivation") }}</h3> 22 <h3>{{_("Motivation") }}</h3>
20 <p> 23 <p>
21 {% trans %} 24 {% trans %}
22 cURL supports a bunch of crypto backends. GNUnet requires the use of 25 cURL supports many crypto backends. GNUnet requires the use of
23 GnuTLS, but other variants are used by some distributions. Supporting 26 GnuTLS, but other variants are used by some distributions. Supporting
24 other crypto backends would again expose us to a wider array of 27 other crypto backends would again expose us to a wider array of
25 security issues, may create licensing issues and most importantly 28 security issues, may create licensing issues and most importantly
@@ -71,16 +74,6 @@
71 </p> 74 </p>
72 <h3>{{_("Rename to fix") }}</h3> 75 <h3>{{_("Rename to fix") }}</h3>
73 <p> 76 <p>
74 {% trans %}
75 At this point, developers that don't want to rebuild an entire
76 distribution from scratch get grumpy. Grumpy developers do silly
77 things, like forking code to fix it. I called the fork gnurl (to be
78 pronounced with a grumpy voice and an emphasis on the R) as it is bits
79 of cURL, a bit more GNUish, for GnuNet, and gnurl can be pronounced to
80 indicate the grumpy origins.
81 {% endtrans %}
82 </p>
83 <p>
84 {% trans %} 77 {% trans %}
85 How does forking fix it? Easy. First, we can get rid of all of the 78 How does forking fix it? Easy. First, we can get rid of all of the
86 compatibility issues --- if you use libgnurl, you state that you don't 79 compatibility issues --- if you use libgnurl, you state that you don't
@@ -113,6 +106,7 @@
113 no additions to the original curl source have been written. 106 no additions to the original curl source have been written.
114 {% endtrans %} 107 {% endtrans %}
115 </p> 108 </p>
109 <h4>{{_("Gotchas") }}</h4>
116 <p> 110 <p>
117 {% trans %} 111 {% trans %}
118 libgnurl and gnurl are not intended to be used as a replacement 112 libgnurl and gnurl are not intended to be used as a replacement