eBookReaderSwitch/thirdparty/curl/packages
Moroni Granja 98d9d7be17 Squashed 'mupdf/' content from commit 340abaf66
git-subtree-dir: mupdf
git-subtree-split: 340abaf66f43a04477866e5df8ba9726709f43f4
2019-10-30 13:48:08 -03:00
..
Android Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
DOS Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
OS400 Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
Symbian Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
TPF Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
vms Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
Makefile.am Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03:00
README Squashed 'mupdf/' content from commit 340abaf66 2019-10-30 13:48:08 -03: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.