curl/packages
Daniel Gustafsson 1460e89e01 vtls: add MesaLink to curl_sslbackend enum
MesaLink support was added in commit 57348eb97d but the
backend was never added to the curl_sslbackend enum in curl/curl.h.
This adds the new backend to the enum and updates the relevant docs.

Closes #3195
Reviewed-by: Daniel Stenberg <daniel@haxx.se>
2018-10-30 16:56:51 +01:00
..
AIX whitespace fixes 2018-09-23 22:24:02 +00:00
Android whitespace fixes 2018-09-23 22:24:02 +00:00
DOS cleanup: misc typos in strings and comments 2018-03-16 11:08:31 +01:00
Linux whitespace fixes 2018-09-23 22:24:02 +00:00
NetWare whitespace fixes 2018-09-23 22:24:02 +00:00
OS400 vtls: add MesaLink to curl_sslbackend enum 2018-10-30 16:56:51 +01:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian whitespace fixes 2018-09-23 22:24:02 +00:00
TPF whitespace fixes 2018-09-23 22:24:02 +00:00
Win32 whitespace fixes 2018-09-23 22:24:02 +00:00
vms whitespace fixes 2018-09-23 22:24:02 +00:00
Makefile.am whitespace fixes 2018-09-23 22:24:02 +00:00
README removed trailing whitespace 2010-02-14 19:40:18 +00:00

README

                                  _   _ ____  _
                              ___| | | |  _ \| |
                             / __| | | | |_) | |
                            | (__| |_| |  _ <| |___
                             \___|\___/|_| \_\_____|

PACKAGES

 This directory and all its subdirectories are for special package
information, template, scripts and docs. The files herein should be of use for
those of you who want to package curl in a binary or source format using one
of those custom formats.

 The hierarchy for these directories is something like this:

   packages/[OS]/[FORMAT]/

 Currently, we have Win32 and Linux for [OS]. There might be different formats
for the same OS so for Linux we have RPM as format.

 We might need to add some differentiation for CPU as well, as there is
Linux-RPMs for several CPUs. However, it might not be necessary since the
packaging should be pretty much the same no matter what CPU that is used.

 For each unique OS-FORMAT pair, there's a directory to "fill"! I'd like to
see a single README with as much details as possible, and then I'd like some
template files for the package process.