curl/packages
Viktor Szakats 4bd91bc474 spelling fixes
Detected using the `codespell` tool (version 1.13.0).

Also secure and fix an URL.
2018-06-03 12:14:45 +00:00
..
AIX spelling fixes 2017-03-26 23:56:23 +02:00
Android includes: remove curl/curlbuild.h and curl/curlrules.h 2017-06-14 11:07:33 +02:00
DOS cleanup: misc typos in strings and comments 2018-03-16 11:08:31 +01:00
EPM spelling fixes 2017-03-26 23:56:23 +02:00
Linux URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
NetWare URLs: change all http:// URLs to https:// 2016-02-03 00:19:02 +01:00
OS400 os400: add new option in ILE/RPG binding 2018-05-31 19:08:03 +02:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian Curl_range: commonize FTP and FILE range handling 2018-01-30 17:23:26 +01:00
TPF openssl: remove all uses of USE_SSLEAY 2015-03-05 10:57:52 +01:00
Win32 docs/comments: Update to secure URL versions 2017-08-08 21:41:07 +02:00
vms spelling fixes 2018-06-03 12:14:45 +00:00
Makefile.am build: move Android.mk to packages/Android/ 2013-02-06 23:08:05 +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.