1
0
mirror of https://github.com/moparisthebest/curl synced 2024-11-14 05:25:06 -05:00
curl/packages
2010-06-09 17:19:58 +02:00
..
AIX remove all .cvsignore files 2010-03-25 23:22:03 +01:00
DOS remove all .cvsignore files 2010-03-25 23:22:03 +01:00
EPM remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Linux remove all .cvsignore files 2010-03-25 23:22:03 +01:00
NetWare remove the CVSish $Id$ lines 2010-03-24 11:02:54 +01:00
OS400 ILE/RPG binding updated to current curl.h definitions. 2010-06-09 17:19:58 +02:00
Solaris remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Symbian add missing new files to non-configure target build files 2010-06-02 15:09:39 +02:00
TPF add missing new files to non-configure target build files 2010-06-02 15:09:39 +02:00
vms remove all .cvsignore files 2010-03-25 23:22:03 +01:00
Win32 remove all .cvsignore files 2010-03-25 23:22:03 +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

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

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.