curl/packages
Dan Fandrich 205f8b266c Fixed LDAP library file name bug (KNOWN_BUGS #1). configure now auto-detects
the correct dynamic library names by default, and provides override switches
--with-ldap-lib, --with-lber-lib and --without-lber-lib.  Added
CURL_DISABLE_LDAP to platform-specific config files to disable LDAP
support on those platforms that probably don't have dynamic OpenLDAP
libraries available to avoid compile errors.
2005-03-11 05:28:07 +00:00
..
DOS Added option for using C-ares and libidn. 2004-12-17 12:38:06 +00:00
EPM Markus F.X.J. Oberhumer's cvsignore fixes 2002-08-22 19:46:39 +00:00
Linux P R Schaffner updated this to work for 7.11.0 2004-02-09 10:24:55 +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
vms Fixed LDAP library file name bug (KNOWN_BUGS #1). configure now auto-detects 2005-03-11 05:28:07 +00:00
Win32 Removed libcurl.def 2004-11-09 14:55:23 +00:00
.cvsignore things to ignore 2002-08-08 23:09:45 +00:00
Makefile.am Günter Knauf's NetWare changes. 2004-03-17 12:46:42 +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.