1
0
mirror of https://github.com/moparisthebest/curl synced 2024-12-21 23:58:49 -05:00
curl/packages
Kamil Dudka 6ad3add606 vtls: support TLS 1.3 via CURL_SSLVERSION_TLSv1_3
Fully implemented with the NSS backend only for now.

Reviewed-by: Ray Satiro
2016-11-07 11:52:07 +01:00
..
AIX s/cURL/curl 2016-11-07 10:36:23 +01:00
Android build: Renamed CURLX_ONES file list definition to CURLX_CFILES 2014-05-21 23:11:51 +01:00
DOS s/cURL/curl 2016-11-07 10:36:23 +01:00
EPM code/docs: Use Unix rather than UNIX to avoid use of the trademark 2014-12-26 21:42:44 +00:00
Linux URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
NetWare URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
OS400 vtls: support TLS 1.3 via CURL_SSLVERSION_TLSv1_3 2016-11-07 11:52:07 +01:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian s/cURL/curl 2016-11-07 10:36:23 +01:00
TPF openssl: remove all uses of USE_SSLEAY 2015-03-05 10:57:52 +01:00
vms s/cURL/curl 2016-11-07 10:36:23 +01:00
Win32 s/cURL/curl 2016-11-07 10:36:23 +01:00
Makefile.am build: move Android.mk to packages/Android/ 2013-02-06 23:08:05 +01:00
README removed trailing whitespace 2010-02-14 19:40:18 +00:00

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

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.