moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-12-23 00:28:48 -05:00
Code Issues Releases Wiki Activity
3e0a8e539c
curl/packages
History
Patrick Monnerat 3e0a8e539c os400: getpeername() and getsockname() return ebcdic AF_UNIX sockaddr, 
As libcurl now uses these 2 system functions, wrappers are needed on os400
to convert returned AF_UNIX sockaddrs to ascii.

This is a follow-up to commit 7fb54ef.
See also #4037.
Closes #4214
2019-09-24 13:39:22 +02:00
..
Android whitespace fixes 2018-09-23 22:24:02 +00:00
DOS openssl: Remove SSLEAY leftovers 2018-11-17 21:36:10 +01:00
OS400 os400: getpeername() and getsockname() return ebcdic AF_UNIX sockaddr, 2019-09-24 13:39:22 +02:00
Symbian axtls: removed 2018-11-01 10:29:53 +01:00
TPF whitespace fixes 2018-09-23 22:24:02 +00:00
vms openssl: define HAVE_SSL_GET_SHUTDOWN based on version number 2019-07-14 16:24:46 +02:00
Makefile.am packages: remove old leftover files and dirs 2018-12-05 15:29:24 +01:00
README removed trailing whitespace 2010-02-14 19:40:18 +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.