curl/packages
Dan Fandrich 542507f316 Tweak the Android.mk file for its new location
This is untested, but ought to be enough to still allow it
to work automatically when the entire curl source tree is
dropped into a full Android source tree.
2013-02-06 23:44:49 +01:00
..
AIX add newly created manual page 2012-04-27 20:25:35 +02:00
Android Tweak the Android.mk file for its new location 2013-02-06 23:44:49 +01:00
DOS packages/DOS/common.dj: remove COFF debug info generation 2013-01-10 19:58:59 +01:00
EPM add newly created manual page 2012-04-27 20:25:35 +02: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 Makefile.inc: fix $(top_srcdir) not allowed in _SOURCES variables 2013-01-20 04:20:02 +01:00
Solaris
Symbian Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
TPF Changed the TPF make file to get source files from Makefile.inc 2010-09-27 17:47:20 -07:00
vms VMS: fix and generate the VMS build config 2013-02-05 23:08:57 +01:00
Win32
Makefile.am build: move Android.mk to packages/Android/ 2013-02-06 23:08:05 +01: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.