mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-15 06:40:09 +08:00
Code Issues Packages Projects Releases Wiki Activity
985bd18904
curl/packages
History
Yang Tse 267b942383 configure script now checks availability of the inet_ntop() function, 
and when not crosscompiling verifies if it is IPv6 capable.

HAVE_INET_NTOP will only be defined when an IPv6 capable working
inet_ntop function is available.
2008-09-24 16:43:40 +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
NetWare fixed link to latest native awk. 2008-01-24 15:39:51 +00:00
OS400 ntoa() and inet_ntoa_r() no longer used 2008-09-24 12:22:16 +00:00
Solaris
Symbian Minor Symbian updates. 2008-07-30 00:10:32 +00:00
vms configure script now checks availability of the inet_ntop() function, 2008-09-24 16:43:40 +00:00
Win32
.cvsignore
Makefile.am Updated Symbian UIDs. Added .pkg files for creating .sis packages. 2008-04-25 22:49:18 +00:00
README

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.