curl/packages
Yang Tse bcd8a3b240 Define HAVE_SIGNAL_H, HAVE_SIG_ATOMIC_T and HAVE_SIG_ATOMIC_T_VOLATILE
as appropriate for platforms that don't have autotools support
2006-11-24 16:38:58 +00:00
..
AIX cvsignore these files 2006-05-10 14:16:30 +00:00
DOS Added option for using C-ares and libidn. 2004-12-17 12:38:06 +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 added some lines to fetch ares version. 2004-07-11 17:59:07 +00:00
Solaris things to ignore 2002-08-08 23:09:45 +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 Define HAVE_SIGNAL_H, HAVE_SIG_ATOMIC_T and HAVE_SIG_ATOMIC_T_VOLATILE 2006-11-24 16:38:58 +00:00
.cvsignore things to ignore 2002-08-08 23:09:45 +00:00
Makefile.am fixed the AIX packages 2006-03-20 07:59:45 +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.