From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [RFC 3/3] doc: Add a section on gbp-compatible packages
Date: Fri, 27 Aug 2021 10:07:01 +0200 [thread overview]
Message-ID: <20210827080701.5099-4-ubely@ilbers.de> (raw)
In-Reply-To: <20210827080701.5099-1-ubely@ilbers.de>
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
doc/user_manual.md | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index 1da0e9d..c58d8c8 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -786,6 +786,21 @@ This approach prevents duplication of the license files in different packages.
The last line in the example above adds recipe to the Isar work chain.
+### Compilation of sources from gbp-compatible repository
+
+gbp or git-buildpackage is a utility that supports maintaining a Debian/Ubuntu package in git. Such kind of repositories can be found on salsa. They might be useful for building unreleased or older packages and patching them. The bbclass for this approach is called `dpkg-gbp`.
+
+#### Example
+```
+inherit dpkg-gbp
+
+SRC_URI = "git://salsa.debian.org/debian/cowsay.git;protocol=https"
+SRC_URI += "file://isar.patch"
+SRCREV = "756f0c41fbf582093c0c1dff9ff77734716cb26f"
+```
+
+For these packages `git` is used as a PATCHTOOL. This means that custom patches should be in format that allows to apply them by `git am` command.
+
### Compilation of sources missing the debian/-directory
The `debian` directory contains meta information on how to build a package from source. This is roughly speaking "configure", "compile", "install" all described in a Debian-specific way.
--
2.20.1
prev parent reply other threads:[~2021-08-27 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 8:06 [RFC 0/3] Fix gbp patching after configuration change Uladzimir Bely
2021-08-27 8:06 ` [RFC 1/3] meta-isar: reformat isar.patch for cowsay to properly work with git Uladzimir Bely
2021-08-27 8:07 ` [RFC 2/3] ci: Test for rebuild with no cleanup after configuration change Uladzimir Bely
2021-08-27 8:07 ` Uladzimir Bely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210827080701.5099-4-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox