From 6907bcb4f2f70313def85ec382c5f0d3effcf97c Mon Sep 17 00:00:00 2001
From: Miroslav Suchý <msuchy@redhat.com>
Date: Apr 13 2022 16:49:20 +0000
Subject: doc: document why we do not use src.rpm in Custom method


---

diff --git a/doc/custom_source_method.rst b/doc/custom_source_method.rst
index 3c6274f..28955be 100644
--- a/doc/custom_source_method.rst
+++ b/doc/custom_source_method.rst
@@ -77,6 +77,13 @@ Since this all is in user's hands, it is not technically incorrect to have empty
 hook payload, e.g. it is valid to call `curl -X POST <THE_CUSTOM_HOOK_URL>` to
 trigger the custom source build method.
 
+Src.RPM
+-------
+
+Copr expects that `script` creates SPEC file, tar ball, and patches in the working
+directory. We cannot process SRC.RPM. Because some chroots can use technology
+which our server cannot recognize. E.g., in the past `rpm` changed compression and
+checksum algorithm and rpm from RHEL was unable to process packages from Fedora.
 
 Examples
 --------
@@ -93,6 +100,20 @@ Examples
 
     $ copr build-package --name quick-package PROJECT # trigger the build
 
+- Trivial example (use SRC.RPM)::
+
+    $ cat script
+    #! /bin/sh -x
+    make dist-srpm
+    rpmdev-extract redhat/rpm/SRPMS/quick-package-*.src.rpm
+    mv quick-package*src/* ./
+
+    $ copr add-package-custom PROJECT \
+            --name quick-package \
+            --script-builddeps "make rpmdevtools" \
+            --script script
+
+    $ copr build-package --name quick-package PROJECT # trigger the build
 
 - Simple example with Python package with git submodules and in-tree sources::