curl/packages
Johannes Schindelin 9d96a5f0b5
version: add the CURL_VERSION_MULTI_SSL feature flag
This new feature flag reports When cURL was built with multiple SSL
backends.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2017-08-28 22:56:49 +02:00
..
AIX spelling fixes 2017-03-26 23:56:23 +02:00
Android includes: remove curl/curlbuild.h and curl/curlrules.h 2017-06-14 11:07:33 +02:00
DOS s/cURL/curl 2016-11-07 10:36:23 +01:00
EPM spelling fixes 2017-03-26 23:56:23 +02: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 version: add the CURL_VERSION_MULTI_SSL feature flag 2017-08-28 22:56:49 +02:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian spelling fixes 2017-03-26 23:56:23 +02:00
TPF openssl: remove all uses of USE_SSLEAY 2015-03-05 10:57:52 +01:00
Win32 docs/comments: Update to secure URL versions 2017-08-08 21:41:07 +02:00
vms docs/comments: Update to secure URL versions 2017-08-08 21:41:07 +02: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

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.