Changes between Version 34 and Version 35 of RpmHowToPackagers

Timestamp:

Mar 31, 2015, 8:08:21 PM (10 years ago)

Author:

dmik

Comment:

Add Taking sources from source repositories and SVN snippets.

RpmHowToPackagers

@@ -165 +165 @@
 All output files will be written in the %HOME%\rpmbuild tree, regardless of current directory and drive.
 
+== Taking sources from source repositories ==
+
+It's a common practice that the program sources to build the RPM packages are taken from a tarball (referred to by the `Source:` keyword in the `.spec` file) which is provided by the program vendor and then stored in the source RPM. It works fine when the packages are built from the vendor sources w/o any modifications but this is rarely a case on OS/2. On OS/2, we don't push our patches upstream (for many reasons) and instead host our own repositories for programs that we support where we manage our patches (many of the programs are located here: http://trac.netlabs.org/ports/).
+
+Given this, using the tarball approach on OS/2 requires to pull a set of patches from our own source repository and apply it to the vendor's tarball to make the program work on OS/2 each time a new change is made. This requires a lot of manual work and is very inconvenient when dealing with a large number of packages. For this reason, it is strongly recommended to write `.spec` files that download the sources directly from the source repositories rather than use tarballs and patch files. This may be achieved with a very simple block of commands.
+
+Note that one should not worry too much about the network speed and traffic issues when using this approach since the sources are downloaded only once for each given repository revision; any subsequent attempt to build a package form the same revision will simply use the source ZIP created when the revision is fetched for the first time w/o involving any network connection. There is also a possibility to use local working copies to fetch the sources from instead of online repositories (see below).
+
+=== SVN ===
+
+The snippets below assume our http://trac.netlabs.org/ports/ source repository layout. They are taken from  this real-life [http://trac.netlabs.org/rpm/browser/spec/trunk/SPECS/libtool.spec?rev=471 spec file].
+
+Paste this block after the main keyword block and before the `%description` field for the main package:
+{{{
+%define svn_url     http://svn.netlabs.org/repos/ports/libtool/trunk
+%define svn_rev     891
+
+Source: %{name}-%{version}%{?svn_rev:-r%{svn_rev}}.zip
+
+BuildRequires: gcc make subversion zip
+}}}
+
+Paste this block instead of the usual `%prep / %setup / %patch` sequence:
+{{{
+%prep
+%if %{?svn_rev:%(sh -c 'if test -f "%{_sourcedir}/%{name}-%{version}-r%{svn_rev}.zip" ; then echo 1 ; else echo 0 ; fi')}%{!?svn_rev):0}
+%setup -q
+%else
+%setup -n "%{name}-%{version}" -Tc
+svn export %{?svn_rev:-r %{svn_rev}} %{svn_url} . --force
+rm -f "%{_sourcedir}/%{name}-%{version}%{?svn_rev:-r%{svn_rev}}.zip"
+(cd .. && zip -SrX9 "%{_sourcedir}/%{name}-%{version}%{?svn_rev:-r%{svn_rev}}.zip" "%{name}-%{version}")
+%endif
+}}}
+
+In order to use the working copy instead of the URL (useful for creating test packages during development) one modifies the first snippet to something like this:
+{{{
+%define svn_url     D:/Coding/ports/libtool/trunk
+#%define svn_rev     891
+}}}
+
+Note the commented out `svn_rev` variable — this causes the local changes from the working copy to be picked up. If `svn_rev` is not commented out then the specified revision w/o any local modifications will be used (the same way as when giving an URL; the only difference is that no network connection is required given that the specified revision is already contained in the working copy).
+
 == Handling documentation in Info format ==