|
28.
|
|
|
archpath - output arch (tla/Bazaar) archive names, with support for branches
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:4
|
|
29.
|
|
|
B<archpath>
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:6
|
|
30.
|
|
|
B<archpath> I<branch>
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:9
|
|
31.
|
|
|
B<archpath> I<branch>--I<version>
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:12
|
|
32.
|
|
|
B<archpath> is intended to be run in an arch (tla or Bazaar) working copy.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:15
|
|
33.
|
|
|
In its simplest usage, B<archpath> with no parameters outputs the package name (archive/category--branch--version) associated with the working copy.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:20
|
|
34.
|
|
|
If a parameter is given, it may either be a branch--version, in which case B<archpath> will output a corresponding package name in the current archive and category, or a plain branch name (without \(oq--"), in which case B<archpath> will output a corresponding package name in the current archive and category and with the same version as the current working copy.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:28
|
|
35.
|
|
|
This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a command like this:
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:32
|
|
36.
|
|
|
CW<baz branch $(archpath) $(archpath new-feature)>
|
|
|
type: Plain text
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:37
|
|
37.
|
|
|
Or if you want to tag your current code onto a \(oqreleases\(cq branch as version 1.0, you might use a command like this:
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../scripts/archpath.1:43
|