curl/packages
Steve Holme b40e37f93d endian: Fixed Linux compilation issues
Having files named endian.[c|h] seemed to cause issues under Linux so
renamed them both to have the curl_ prefix in the filenames.
2014-12-31 14:02:25 +00:00
..
AIX add newly created manual page 2012-04-27 20:25:35 +02:00
Android build: Renamed CURLX_ONES file list definition to CURLX_CFILES 2014-05-21 23:11:51 +01:00
DOS code/docs: Use Unix rather than UNIX to avoid use of the trademark 2014-12-26 21:42:44 +00:00
EPM code/docs: Use Unix rather than UNIX to avoid use of the trademark 2014-12-26 21:42:44 +00:00
Linux add newly created manual page 2012-04-27 20:25:35 +02:00
NetWare Removed trailing empty strings from awk script. 2012-07-12 00:07:01 +02:00
OS400 OS400: enable NTLM authentication 2014-12-05 18:42:39 +01:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian endian: Fixed Linux compilation issues 2014-12-31 14:02:25 +00:00
TPF Changed the TPF make file to get source files from Makefile.inc 2010-09-27 17:47:20 -07:00
vms code/docs: Use Unix rather than UNIX to avoid use of the trademark 2014-12-26 21:42:44 +00:00
Win32 remove all .cvsignore files 2010-03-25 23:22:03 +01: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

                                  _   _ ____  _
                              ___| | | |  _ \| |
                             / __| | | | |_) | |
                            | (__| |_| |  _ <| |___
                             \___|\___/|_| \_\_____|

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.