curl/packages
Patrick Monnerat 8541d02c96 psl: use latest psl and refresh it periodically
The latest psl is cached in the multi or share handle. It is refreshed
before use after 72 hours.
New share lock CURL_LOCK_DATA_PSL controls the psl cache sharing.
If the latest psl is not available, the builtin psl is used.

Reported-by: Yaakov Selkowitz
Fixes #2553
Closes #2601
2018-05-28 20:37:14 +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 cleanup: misc typos in strings and comments 2018-03-16 11:08:31 +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 psl: use latest psl and refresh it periodically 2018-05-28 20:37:14 +02:00
Solaris
Symbian Curl_range: commonize FTP and FILE range handling 2018-01-30 17:23:26 +01:00
TPF openssl: remove all uses of USE_SSLEAY 2015-03-05 10:57:52 +01:00
vms spelling fixes 2018-02-23 23:29:01 +00:00
Win32 docs/comments: Update to secure URL versions 2017-08-08 21:41:07 +02:00
Makefile.am
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.