README: Format commands and paths
Gioele Barabucci authored 1 year, 1 month ago
Scott Talbert committed 9 months ago
12 | 12 | repository. |
13 | 13 | |
14 | 14 | |
15 | Also, our work is maintaining the debian/ directory, so we decided to track | |
15 | Also, our work is maintaining the `debian/` directory, so we decided to track | |
16 | 16 | only that, and _not_ upstream sources. Therefore, the directory structure for a |
17 | 17 | Haskell package foo is as follows: |
18 | 18 | |
22 | 22 | /p/haskell-foo/debian/control -- the usual files |
23 | 23 | ... |
24 | 24 | |
25 | In particular, /p/haskell-foo/ contains no files besides debian/. So what is | |
26 | the point of having the files under the debian/ subdirectory? This way, you can | |
27 | extract the upstream sources in there and run your usual | |
28 | uscan/debchange/quilt/sbuild/debrelease-commands as usual. The `.gitignore` | |
29 | file is set up so that git will not bother you about the extracted upstream | |
30 | sources. | |
25 | In particular, `/p/haskell-foo/` contains no files besides `debian/`. | |
26 | So what is the point of having the files under the `debian/` subdirectory? | |
27 | This way, you can extract the upstream sources in there and run your usual | |
28 | `uscan`/`debchange`/`quilt`/`sbuild`/`debrelease-commands` as usual. | |
29 | The `.gitignore` file is set up so that git will not bother you about the | |
30 | extracted upstream sources. | |
31 | 31 | |
32 | As running uscan or dpkg-buildpackage in that directory will dump files into | |
33 | the parent, we introduced the /p/ directory. Again, a `.gitignore` file is set | |
32 | As running `uscan` or `dpkg-buildpackage` in that directory will dump files into | |
33 | the parent, we introduced the `/p/` directory. Again, a `.gitignore` file is set | |
34 | 34 | up so that git will not bother you about the tarballs, `deb`-files or |
35 | 35 | `changes`-files therein. |
36 | 36 | |
75 | 75 | or `git://salsa.debian.org/haskell-team/pkg-haskell-tools.git` for |
76 | 76 | read-only access). |
77 | 77 | |
78 | All tools are under the `dht` prefix, and it has a manpage (man dht) or at | |
78 | All tools are under the `dht` prefix, and it has a manpage (`man dht`) or at | |
79 | 79 | <file:///usr/share/doc/pkg-haskell-tools/dht.html>. |
80 | 80 | |
81 | 81 |