curl/packages
Steve Holme f0bdd72c10 http_ntlm: Renamed from curl_ntlm.[c|h]
Renamed the header and source files for this module as they are HTTP
specific and as such, they should use the naming convention as other
HTTP authentication source files do - this revert commit 260ee6b7bf.

Note: We could also rename curl_ntlm_wb.[c|h], however, the Winbind
code needs separating from the HTTP protocol and migrating into the
vauth directory, thus adding support for Winbind to the SASL based
protocols such as IMAP, POP3 and SMTP.
2016-03-27 17:58:50 +01:00
..
AIX URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
Android
DOS
EPM
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 os400: Fix ILE/RPG definition of CURLOPT_TFTP_NO_OPTIONS 2016-02-24 13:19:10 +01:00
Solaris
Symbian http_ntlm: Renamed from curl_ntlm.[c|h] 2016-03-27 17:58:50 +01:00
TPF
vms URLs: Change more haxx.se URLs from http: to https: 2016-02-03 01:45:21 +01:00
Win32 URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01: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.