Changes between Version 35 and Version 36 of RpmHowToPackagers

Timestamp:

Jul 1, 2015, 2:18:43 PM (9 years ago)

Author:

dmik

Comment:

Added info about downloading sources from Git and Github

RpmHowToPackagers

@@ -208 +208 @@
 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).
 
+=== Git ===
+
+Projects that use git may be handled similarly but they have their own specifics. There is currently no real-life example of such a project in our repositories but let's assume there is a project called `foobar` with a remote repository at  `git://mygitserver.com`.
+
+Paste this block after the main keyword block and before the `%description` field for the main package:
+{{{
+%define git_url     git://mygitserver.com/foobar.git
+%define git_rev     mytag
+
+Source: %{name}-%{git_rev}.zip
+
+BuildRequires: gcc make git zip
+}}}
+
+Paste this block instead of the usual `%prep / %setup / %patch` sequence:
+{{{
+%prep
+%if %(sh -c 'if test -f "%{_sourcedir}/%{name}-%{git_rev}.zip" ; then echo 1 ; else echo 0 ; fi')
+%setup -q
+%else
+%setup -n "%{name}-%{version}" -Tc
+rm -f "%{_sourcedir}/%{name}-%{git_rev}.zip"
+git archive --format zip --output "%{_sourcedir}/%{name}-%{git_rev}.zip" --prefix "%{name}-%{version}/" --remote "%{git_url}" "%{git_rev}"
+unzip "%{name}-%{git_rev}.zip" -d ..
+%endif
+}}}
+
+Note that you may use your local clone instead of the remote repository as well as with SVN to save some traffic. The URL in this case should be something like `file://D:/Coding/foobar`.
+
+=== Github ===
+
+If a project is hosted at [http://github.com github], we will need to use `curl` instead of `git archive` because github does not support the `archive` command and instead provides a special URL for downloading ZIPs of the tree at any given commit or tag. The snippets below are based on this real-life [http://trac.netlabs.org/rpm/browser/spec/trunk/SPECS/libkai.spec?rev=576 spec file].
+
+Paste this block after the main keyword block and before the `%description` field for the main package:
+{{{
+%define github_name kai
+%define github_url  https://github.com/komh/%{github_name}/archive
+%define github_rev  kai-%{version}
+
+Source: %{github_name}-%{github_rev}.zip
+
+BuildRequires: gcc make curl zip
+}}}
+
+Paste this block instead of the usual `%prep / %setup / %patch` sequence:
+{{{
+%prep
+%if %(sh -c 'if test -f "%{_sourcedir}/%{github_name}-%{github_rev}.zip" ; then echo 1 ; else echo 0 ; fi')
+%setup -n "%{github_name}-%{github_rev}" -q
+%else
+%setup -n "%{github_name}-%{github_rev}" -Tc
+rm -f "%{_sourcedir}/%{github_name}-%{github_rev}.zip"
+curl -sSL "%{github_url}/%{github_rev}.zip" -o "%{_sourcedir}/%{github_name}-%{github_rev}.zip"
+unzip "%{_sourcedir}/%{github_name}-%{github_rev}.zip" -d ..
+%endif
+}}}
+
+Note that due to github naming specifics (and especially if the github's project name doesn't match the RPM package name, (like `kai` vs `libkai` in the example above), the source ZIP will have a name that differs from the usual `%{name}-%{version}` scheme (in the example above it will be `kai-kai-1.1.4.zip` rather than `libkai-1.1.4.zip`).
+
+You could use your local clone instead of the remote repository here as well but in this case magic github URLs for downloading ZIPs won't work so you will have to use the `git archive` command as in the [#Git] section above which is not very practical because you will have to make a lot of temporary changes to your `.spec` file which you will have to revert before committing it to the SPEC repo.
+
 == Handling documentation in Info format ==