curl/packages
Yang Tse 04ca9aecd1 metalink: build fixes and adjustments I 2012-06-07 23:50:12 +02:00
..
AIX add newly created manual page 2012-04-27 20:25:35 +02:00
DOS remove all .cvsignore files 2010-03-25 23:22:03 +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 remove the CVSish $Id$ lines 2010-03-24 11:02:54 +01:00
OS400 OS400/initscript.sh: fix db2_name() module name generation 2012-04-12 19:13:23 +02:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian metalink: build fixes and adjustments I 2012-06-07 23:50:12 +02: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 sources: update source headers 2011-03-10 12:04:33 +01:00
Makefile.am removed trailing whitespace 2010-02-14 19:40:18 +00: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.