gigaset_elements_bl26_opens.../src/opensource/curl/packages
Harald Welte 2957ad7bef initial checkin
taken from https://www.gigaset.com/de_de/cms/lp/open-source.html
specifically
https://cms.gigaset.com/opensource/GigasetElements/gigaset_elements_bl26_opensource.tar.gz
2022-12-11 22:58:24 +01:00
..
AIX initial checkin 2022-12-11 22:58:24 +01:00
Android initial checkin 2022-12-11 22:58:24 +01:00
DOS initial checkin 2022-12-11 22:58:24 +01:00
EPM initial checkin 2022-12-11 22:58:24 +01:00
Linux initial checkin 2022-12-11 22:58:24 +01:00
NetWare initial checkin 2022-12-11 22:58:24 +01:00
OS400 initial checkin 2022-12-11 22:58:24 +01:00
Solaris initial checkin 2022-12-11 22:58:24 +01:00
Symbian initial checkin 2022-12-11 22:58:24 +01:00
TPF initial checkin 2022-12-11 22:58:24 +01:00
Win32 initial checkin 2022-12-11 22:58:24 +01:00
vms initial checkin 2022-12-11 22:58:24 +01:00
Makefile.am initial checkin 2022-12-11 22:58:24 +01:00
Makefile.in initial checkin 2022-12-11 22:58:24 +01:00
README initial checkin 2022-12-11 22:58:24 +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.