curl/packages
Daniel Gustafsson d25f0a42e8
os400.c: fix ASSIGNWITHINCONDITION checksrc warnings
All occurrences of assignment within conditional expression in
os400sys.c rewritten into two steps: first assignment and then the check
on the success of the assignment. Also adjust related incorrect brace
positions to match project indentation style.

This was spurred by seeing "if((inp = input_token))", but while in there
all warnings were fixed.

There should be no functional change from these changes.

Closes #2525
2018-04-25 09:25:12 +02:00
..
AIX
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
Linux
NetWare
OS400 os400.c: fix ASSIGNWITHINCONDITION checksrc warnings 2018-04-25 09:25:12 +02:00
Solaris
Symbian Curl_range: commonize FTP and FILE range handling 2018-01-30 17:23:26 +01:00
TPF
vms spelling fixes 2018-02-23 23:29:01 +00:00
Win32 docs/comments: Update to secure URL versions 2017-08-08 21:41:07 +02:00
Makefile.am
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.