d/README.source: Update data to reflect current state
Carsten Schoenert
1 year, 4 months ago
| 0 | The test-example.tar.xz archive contains the contents of test/example, | |
| 1 | used during build-time tests. | |
| 0 | This package is maintained with git-buildpackage(1). It follows DEP-14 for | |
| 1 | branch naming (e.g. using debian/master for the current version in Debian | |
| 2 | unstable due Debian Python team policy). | |
| 2 | 3 | |
| 3 | test/example is taken from the upstream git repository at | |
| 4 | https://gitlab.freedesktop.org/xdg/pyxdg | |
| 4 | It uses pristine-tar(1) to store enough information in git to generate bit | |
| 5 | identical tarballs when building the package without having downloaded an | |
| 6 | upstream tarball first. | |
| 5 | 7 | |
| 6 | It is not provided in the upstream tarball at | |
| 7 | https://pypi.org/project/pyxdg/ | |
| 8 | When working with patches it is recommended to use "gbp pq import" to import | |
| 9 | the patches, modify the source and then use "gbp pq export --commit" to commit | |
| 10 | the modifications. | |
| 11 | ||
| 12 | The changelog is generated using "gbp dch" so if you submit any changes don't | |
| 13 | bother to add changelog entries but rather provide a nice git commit message | |
| 14 | that can then end up in the changelog. | |
| 15 | ||
| 16 | It is recommended to build the package with pbuilder using: | |
| 17 | ||
| 18 | gbp buildpackage --git-pbuilder | |
| 19 | ||
| 20 | For information on how to set up a pbuilder environment see the git-pbuilder(1) | |
| 21 | manpage. In short: | |
| 22 | ||
| 23 | DIST=sid git-pbuilder create | |
| 24 | gbp clone https://salsa.debian.org/python-team/packages/pyxdg.git | |
| 25 | cd pyxdg | |
| 26 | gbp buildpackage --git-pbuilder | |
| 27 | ||
| 28 | PyXDG is in a so called maintenance mode by upstream. Means the usptream | |
| 29 | maintainer is trying to get this package able to build but is not adding new | |
| 30 | features or changing the behaviour. | |
| 31 | ||
| 32 | The source is also mirrored to GitHub (while writing), so you can find the | |
| 33 | git tree also here: | |
| 34 | ||
| 35 | https://github.com/takluyver/pyxdg | |
| 36 | ||
| 37 | Please avoid filing upstream issues on GitHub, please do so on the project | |
| 38 | home on | |
| 39 | ||
| 40 | https://gitlab.freedesktop.org/xdg/pyxdg | |
| 41 | ||
| 42 | -- Carsten Schoenert <c.schoenert@t-online.de> Mon, 11 Dec 2022 06:56:00 +0100 |