1
0
mirror of https://github.com/moparisthebest/curl synced 2024-11-17 15:05:02 -05:00
curl/packages
Daniel Stenberg f4873ebd0b
krb5: merged security.c and krb specific FTP functions in here
These two files were always tightly connected and it was hard to
understand what went into which. This also allows us to make the
ftpsend() function static (moved from ftp.c).

Removed security.c
Renamed curl_sec.h to krb5.h

Closes #5987
2020-09-21 23:31:39 +02:00
..
Android copyright: fix out-of-date copyright ranges and missing headers 2020-03-24 15:05:59 +01:00
DOS copyright: fix out-of-date copyright ranges and missing headers 2020-03-24 15:05:59 +01:00
OS400 windows: add unicode to feature list 2020-07-14 08:30:17 +00:00
Symbian krb5: merged security.c and krb specific FTP functions in here 2020-09-21 23:31:39 +02:00
TPF copyright: fix out-of-date copyright ranges and missing headers 2020-03-24 15:05:59 +01:00
vms all: fix codespell errors 2020-05-25 19:44:04 +00:00
Makefile.am copyright: fix out-of-date copyright ranges and missing headers 2020-03-24 15:05:59 +01:00
README removed trailing whitespace 2010-02-14 19:40:18 +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.