curl/packages
John Malmberg 10afe7cf10 VMS: Add RELEASE-NOTES to vms document
Add the curl release notes to the release note document generated for
VMS packages.

Add the different filenames generated by a daily build to the
cleanup procedures.
2013-08-15 10:57:52 +02: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 OS400: sync ILE/RPG binding with current curl.h 2013-07-24 16:12:35 +02:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
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
Win32 remove all .cvsignore files 2010-03-25 23:22:03 +01:00
vms VMS: Add RELEASE-NOTES to vms document 2013-08-15 10:57:52 +02: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.