curl/packages
Patrick Monnerat 501f9f8309 Fix definition of CURLOPT_SOCKS5_GSSAPI_SERVICE from LONG to OBJECTPOINT
Fix OS400 makefile for tests to use the new Makefile.inc in libtest
Update the OS400 wrappers and RPG binding according to the current CVS source state
2009-08-11 14:07:08 +00:00
..
AIX Makefile.am was lost 2009-05-09 12:11:32 +00:00
DOS add default USE_CURLDEBUG setting 2009-06-13 20:47:19 +00:00
EPM
Linux
NetWare fixed link to latest native awk. 2008-01-24 15:39:51 +00:00
OS400 Fix definition of CURLOPT_SOCKS5_GSSAPI_SERVICE from LONG to OBJECTPOINT 2009-08-11 14:07:08 +00:00
Solaris Remove empty line used to force CVS to update the $Id date string format 2009-05-19 12:12:22 +00:00
Symbian Added nonblock.c to the non-automake makefiles (note that the dependencies 2009-07-15 21:49:47 +00:00
TPF Added nonblock.c to the non-automake makefiles (note that the dependencies 2009-07-15 21:49:47 +00:00
vms renamed generated config.h to curl_config.h in order to avoid clashes when libcurl is used with other projects which also have a config.h. 2009-07-14 13:25:14 +00:00
Win32
.cvsignore
Makefile.am Remove DOS and TPF package's Makefile.am 2009-05-09 12:08:24 +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.