Document repository structure more precisely
Ximin Luo
4 years ago
54 | 54 | |
55 | 55 | REALVER=<old-version> ./update.sh <rust-crate-name> # then |
56 | 56 | REALVER=<old-version> ./release.sh <rust-crate-name> |
57 | ||
58 | ||
59 | Repository structure | |
60 | ==================== | |
61 | ||
62 | `pending-*` branches are managed by `./release.sh`, so please don't manage them | |
63 | yourself as you will interfere with the working of that script. The intention | |
64 | is that they should only differ from the master branch by 1 commit, i.e. the | |
65 | `dch -r` commit created by `./release.sh`. | |
66 | ||
67 | If you want to create separate non-master branches, that is fine - just don't | |
68 | call them `pending-*` and don't run `./release.sh` on those branches. If you | |
69 | want to test your crate, instead run:: | |
70 | ||
71 | cd build && [SOURCEONLY=1] ./build.sh <rust-crate-name> [<old-version>] | |
72 | ||
73 | omitting or not omitting the stuff in [] as needed. | |
57 | 74 | |
58 | 75 | |
59 | 76 | General packaging tips |
200 | 217 | |
201 | 218 | $ ./repackage.sh A |
202 | 219 | $ cd build |
203 | $ ./build.sh A⏎ | |
220 | $ ./build.sh A | |
221 | ||
222 | If this package is already in the archive and you want to recreate that, you | |
223 | will need to use the exact same version of debcargo that was used previously. |