|
30.
|
|
|
B<archpath> is intended to be run in an arch (tla or Bazaar) working copy.
|
|
|
type: Plain text
|
|
|
|
B<archpath> est censé tourner dans une copie de travail arch (tla ou Bazaar).
|
|
Translated by
Julien Cristau
|
|
|
|
|
type: Plain text
|
|
Located in
../scripts/archpath.1:15
|
|
31.
|
|
|
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
|
|
|
|
Le cas d'utilisation le plus simple est le suivant[nbsp] : lancer B<archpath> sans paramètre entraîne l'affichage du nom du paquet (archive/categorie--branche--version) associé à la copie de travail.
|
|
Translated by
Julien Cristau
|
|
|
|
|
type: Plain text
|
|
Located in
../scripts/archpath.1:20
|
|
32.
|
|
|
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
|
|
|
|
Si un paramètre est passé, il peut être soit branche--version, auquel cas B<archpath> affiche le nom du paquet correspondant à l'archive actuelle et la catégorie, soit un nom de branche complet (sans "--"), auquel cas B<archpath> affiche le nom du paquet correspondant dans la même archive, la même catégorie, et à la même version que la copie de travail actuelle.
|
|
Translated by
Xavier Guimard
|
|
|
|
Located in
../scripts/archpath.1:28
|
|
33.
|
|
|
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
|
|
|
|
C'est utile pour la gestion des branches. Par exemple, si vous utilisez Bazaar et que vous voulez créer une branche pour une nouvelle fonctionnalité, vous pouvez utiliser une commande telle que[nbsp] :
|
|
Translated by
taffit
|
|
|
|
Located in
../scripts/archpath.1:32
|
|
34.
|
|
|
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.
|
|
|
|
CW<baz branch $(archpath) $(archpath new-feature)>
|
|
Translated by
Julien Cristau
|
|
|
|
|
type: Plain text
|
|
Located in
../scripts/archpath.1:37
|
|
35.
|
|
|
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
|
|
|
|
Ou si vous voulez marquer votre code actuel comme étant une version 1.0 dans une branche "releases", vous pouvez utiliser une commande telle que[nbsp] :
|
|
Translated by
Xavier Guimard
|
|
|
|
Located in
../scripts/archpath.1:43
|
|
36.
|
|
|
CW<baz branch $(archpath) $(archpath releases--1.0)>
|
|
|
type: Plain text
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
CW<baz branch $(archpath) $(archpath releases--1.0)>
|
|
Translated by
Julien Cristau
|
|
|
|
|
type: Plain text
|
|
Located in
../scripts/archpath.1:48
|
|
37.
|
|
|
That's much easier than using \(oqbaz tree-version\(cq to look up the package name and manually modifying the result.
|
|
|
type: Plain text
|
|
|
|
C'est bien plus commode que d'utiliser "baz tree-version" pour récupérer le nom du paquet puis modifier le résultat manuellement.
|
|
Translated by
Xavier Guimard
|
|
|
|
Located in
../scripts/archpath.1:54
|
|
38.
|
|
|
B<archpath> was written by
|
|
|
type: Plain text
|
|
|
|
B<archpath> a été écrit par
|
|
Translated by
Julien Cristau
|
|
|
|
|
type: Plain text
|
|
Located in
../scripts/archpath.1:57
|
|
39.
|
|
|
Colin Watson E<lt>cjwatson@debian.orgE<gt>.
|
|
|
type: Plain text
|
|
|
|
Colin Watson E<lt>cjwatson@debian.orgE<gt>.
|
|
Translated by
Julien Cristau
|
|
|
|
|
type: Plain text
|
|
Located in
../scripts/archpath.1:59
|