#2171 doc: document why we do not use src.rpm in Custom method
Merged 4 months ago by praiskup. Opened 4 months ago by msuchy.
copr/ msuchy/copr srcrpm  into  main

@@ -77,6 +77,13 @@ 

  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 @@ 

  

      $ 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::

  

no initial comment

Build succeeded.

Perhaps we need '--script-builddeps "make rpmdevtools"' too

rebased onto c65a2f6e783670f83d32f0d17e5ba645d998b768

4 months ago

Build succeeded.

rebased onto 6907bcb

4 months ago

Build succeeded.

Commit e0da1c6 fixes this pull-request

Pull-Request has been merged by praiskup

4 months ago
Metadata