curl/packages
Patrick Monnerat a08b6ae813 Adapt OS400 SSL (qssl.h) to V5R4
Fix qssl.c wrong error message
Upgrade OS400 wrappers and makefiles to 7.18.1
2008-04-07 13:09:17 +00:00
..
AIX cvsignore these files 2006-05-10 14:16:30 +00:00
DOS Added TOPDIR variable. Updated package locations. 2007-02-27 15:22:37 +00:00
EPM Provide 'datarootdir' parameter to shutup configuration warning, 2006-10-21 17:08:48 +00:00
Linux David Shaw finally removed all traces of Gopher and we are now officially 2006-01-16 22:14:37 +00:00
NetWare fixed link to latest native awk. 2008-01-24 15:39:51 +00:00
OS400 Adapt OS400 SSL (qssl.h) to V5R4 2008-04-07 13:09:17 +00:00
Solaris things to ignore 2002-08-08 23:09:45 +00:00
vms Patrick Monnerat modified the LDAP code and approach in curl. Starting now, 2007-08-11 20:57:54 +00:00
Win32 David Shaw finally removed all traces of Gopher and we are now officially 2006-01-16 22:14:37 +00:00
.cvsignore things to ignore 2002-08-08 23:09:45 +00:00
Makefile.am Add the files in the OS400 dir to the dist. I didn't add it as a new subdir 2007-08-23 14:46:37 +00:00
README new package related file 2000-10-31 09:50:22 +00:00

                                  _   _ ____  _     
                              ___| | | |  _ \| |    
                             / __| | | | |_) | |    
                            | (__| |_| |  _ <| |___ 
                             \___|\___/|_| \_\_____|

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.