curl/packages
Yang Tse 65cf30e441 add default USE_CURLDEBUG setting 2009-06-13 20:47:19 +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 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 Adjusted to take in account that... 2009-06-10 02:49:42 +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 new libcurl source files to Symbian OS build files. 2009-04-11 07:06:34 +00:00
TPF Remove DOS and TPF package's Makefile.am 2009-05-09 12:08:24 +00:00
Win32 David Shaw finally removed all traces of Gopher and we are now officially 2006-01-16 22:14:37 +00:00
vms added header inclusion guard 2009-06-11 11:57:46 +00:00
.cvsignore things to ignore 2002-08-08 23:09:45 +00:00
Makefile.am Remove DOS and TPF package's Makefile.am 2009-05-09 12:08:24 +00:00
README new package related file 2000-10-31 09:50:22 +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.