Merge lp:~jelmer/bzr-builder/doc-subst-vars into lp:bzr-builder

Proposed by Jelmer Vernooij
Status: Merged
Merged at revision: 161
Proposed branch: lp:~jelmer/bzr-builder/doc-subst-vars
Merge into: lp:bzr-builder
Diff against target: 38 lines (+25/-4)
1 file modified
__init__.py (+25/-4)
To merge this branch: bzr merge lp:~jelmer/bzr-builder/doc-subst-vars
Reviewer Review Type Date Requested Status
Martin Packman (community) Approve
bzr-builder developers Pending
Review via email: mp+83989@code.launchpad.net

Description of the change

Document the new substitution variables introduced in recipe format 0.4, and clarify the help for {debupstream}.

To post a comment you must log in.
Revision history for this message
Martin Packman (gz) wrote :

+ * {debupstream}/{debupstream:<branch name} will be replaced by the upstream

Missing a '>'.

+ * {latest-tag}/{latest-tag:<branch name} will be replaced with the
+ name of the tag found on the most recent tag on a revision in the
+ branch mainline.

Also missing a '>'. I can't parse this, "tag found on the most recent tag" seems like an error.

Otherwise reads fine.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file '__init__.py'
2--- __init__.py 2011-11-10 17:32:04 +0000
3+++ __init__.py 2011-11-30 18:32:23 +0000
4@@ -123,10 +123,31 @@
5 * {revno} will be the revno of the base branch (the first specified).
6 * {revno:<branch name>} will be substituted with the revno for the
7 branch named <branch name> in the recipe.
8- * {debupstream} will be replaced by the upstream portion of the version
9- number taken from debian/changelog in the final tree. If when the
10- tree is built the top of debian/changelog has a version number of
11- "1.0-1" then this would evaluate to "1.0".
12+ * {debupstream}/{debupstream:<branch name} will be replaced by the upstream
13+ portion of the version number taken from debian/changelog in the branch.
14+ For example, if debian/changelog has a version number of "1.0-1" then this
15+ would evaluate to "1.0".
16+ * {debupstream-base}/{debupstream-base:<branch name>} will be replaced by the
17+ upstream portion of the version number taken from debian/changelog in the
18+ branch, with any VCS markers stripped. For example, if debian/changelog
19+ has a version number of "1.0~bzr43-1" then this would evaluate to "1.0~".
20+ For any upstream versions without a VCS marker, a "+" is added to the
21+ version ("1.0-1" becomes "1.0+").
22+ * {debversion}/{debversion:<branch name>} will be substituted with
23+ the exact version string from debian/changelog in the branch.
24+ * {revtime}/{revtime:<branch name>} will be substituted with the date and
25+ time of the revision that was built, such as 201108191512.
26+ * {revdate}/{revdate:<branch name>} will be substituted with the date
27+ of the revision that was built, such as 20111222.
28+ * {latest-tag}/{latest-tag:<branch name} will be replaced with the
29+ name of the tag found on the most recent tag on a revision in the
30+ branch mainline.
31+ * {git-commit}/{git-commit:<branch name>} will be substituted with the last 7
32+ characters of the SHA1 checksum of the revision that was built, if the
33+ revision was imported from a Git repository.
34+ * {svn-revno}/{svn-revno:<branch name>} will be substituted with the
35+ Subversion revision number of the revision that was built, if the
36+ revision was imported from a Subversion repository.
37
38 Instruction syntax summary:
39

Subscribers

People subscribed via source and target branches