aboutsummaryrefslogtreecommitdiff
path: root/PACKAGERS.md
diff options
context:
space:
mode:
authorHarry Jeffery <harry@exec64.co.uk>2019-01-21 22:56:59 +0000
committerHarry Jeffery <harry@exec64.co.uk>2019-01-29 22:26:22 +0000
commit075bc7705f665326a7e5896c51e8fcabea6cdac6 (patch)
tree958e778e1928e570ec275cc33623922a03d747b8 /PACKAGERS.md
parentc7d76a143c942de9f9556e6a272c3624955b4bb9 (diff)
downloadimv-075bc7705f665326a7e5896c51e8fcabea6cdac6.tar.gz
Add PACKAGERS file
Diffstat (limited to 'PACKAGERS.md')
-rw-r--r--PACKAGERS.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/PACKAGERS.md b/PACKAGERS.md
new file mode 100644
index 0000000..3339174
--- /dev/null
+++ b/PACKAGERS.md
@@ -0,0 +1,29 @@
+# Dear Packager,
+
+This document is a quick summary of all you need to know to package imv for
+your favourite operating system.
+
+## 1. Select backends
+
+imv supports multiple "backends" in a plugin style architecture. Each backend
+provides support for different image formats using different underlying
+libraries. The ones that are right for your operating system depend on which
+formats you need support for, and your licensing requirements.
+
+imv is published under the MIT license, but its backends may have different
+licensing requirements.
+
+You can configure the backends to use in [config.mk](config.mk). Sensible
+defaults are pre-configured to provide maximum coverage with the least overlap
+and fewest dependencies.
+
+## 2. $ make && make install
+
+Once your backends have been configured and you've confirmed the library
+each backend uses is installed, you can simply follow the Installation section
+of the [README](README.md) to build imv.
+
+## 3. Package
+
+Package the resulting binary and man pages in your operating system's native
+package format.