curl/packages
Patrick Monnerat 7639a9cfc9 os400: upgrade ILE/RPG binding 2016-04-22 18:07:11 +02:00
..
AIX URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
Android build: Renamed CURLX_ONES file list definition to CURLX_CFILES 2014-05-21 23:11:51 +01:00
DOS code/docs: Use Unix rather than UNIX to avoid use of the trademark 2014-12-26 21:42:44 +00: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 os400: upgrade ILE/RPG binding 2016-04-22 18:07:11 +02:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian http_ntlm: Renamed from curl_ntlm.[c|h] 2016-03-27 17:58:50 +01:00
TPF openssl: remove all uses of USE_SSLEAY 2015-03-05 10:57:52 +01:00
Win32 URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
vms URLs: Change more haxx.se URLs from http: to https: 2016-02-03 01:45:21 +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

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.