| 1 |
Debian kde-extras Team
|
| 2 |
----------------------
|
| 3 |
|
| 4 |
1. Contacts
|
| 5 |
-----------
|
| 6 |
|
| 7 |
General help requests
|
| 8 |
<debian-kde@lists.debian.org> mailing list
|
| 9 |
#debian-kde on irc
|
| 10 |
|
| 11 |
Packaging queries
|
| 12 |
<debian-qt-kde@lists.debian.org> mailing list
|
| 13 |
#debian-qt-kde on irc
|
| 14 |
|
| 15 |
Maintainers
|
| 16 |
<pkg-kde-extras@lists.alioth.debian.org> mailing list
|
| 17 |
|
| 18 |
|
| 19 |
2. Subversion repository
|
| 20 |
------------------------
|
| 21 |
|
| 22 |
You can browse it only at:
|
| 23 |
|
| 24 |
http://svn.debian.org/wsvn/pkg-kde/kde-extras/
|
| 25 |
|
| 26 |
To "checkout" the repository use these commands:
|
| 27 |
|
| 28 |
$ svn co svn+ssh://${ALIOTH_USERNAME}@svn.debian.org/svn/pkg-kde/kde-extras
|
| 29 |
|
| 30 |
Authorized SSH keys are controlled at https://alioth.debian.org/account/
|
| 31 |
|
| 32 |
The repository layout is:
|
| 33 |
|
| 34 |
- packagename/
|
| 35 |
- trunk/
|
| 36 |
- branches/
|
| 37 |
- tags/
|
| 38 |
- 0.7.2-1/
|
| 39 |
- 0.7.2-2/
|
| 40 |
- 0.7.2-2ubuntu1/
|
| 41 |
- 0.7.2-2ubuntu2/
|
| 42 |
- 0.7.2-2ubuntu3/
|
| 43 |
- 0.8.0/
|
| 44 |
...
|
| 45 |
|
| 46 |
If only one version of the package is available at the time, development must
|
| 47 |
be made at trunk/ dir, copying the dir to tags/'pkg-version' each time a new
|
| 48 |
release is made.
|
| 49 |
|
| 50 |
When, at some point, the need to have two different versions at the same time
|
| 51 |
arises (for example, if we need a version to be in unstable and a different one
|
| 52 |
to be in experimental), experimental development will be made in trunk/ and
|
| 53 |
if a new unstable package needs to be cooked, copying
|
| 54 |
tag/'latest_version_in_sid' to tag/'latest_version_in_sid'+1 will make the
|
| 55 |
trick.
|
| 56 |
|
| 57 |
3. Using svn-buildpackage
|
| 58 |
--------------------------
|
| 59 |
|
| 60 |
Packages with an upstream tarball will require you to set the mergeWithUpstream
|
| 61 |
property first (from the package root) so that svn-buildpackage will look for
|
| 62 |
the .orig.tar.gz in the ../tarballs directory.
|
| 63 |
|
| 64 |
% svn propset mergeWithUpstream 1 debian
|
| 65 |
|
| 66 |
Please note that this only works for packages which have only the debian/
|
| 67 |
directory committed. Consequently, you must use CDBS's simple-patchsys.mk or
|
| 68 |
dpatch to modify the upstream sources.
|
| 69 |
|
| 70 |
After you have finished and committed your Debian patches via
|
| 71 |
|
| 72 |
% svn commit [PACKAGE]
|
| 73 |
|
| 74 |
as well as copying the orig.tar.gz to ../tarballs/ if necessary, you may build
|
| 75 |
your package with the following commands:
|
| 76 |
|
| 77 |
% svn-buildpackage --svn-ignore-new -rfakeroot
|
| 78 |
|
| 79 |
Please, don't commit tarballs/ or build-area/ directories to SVN.
|
| 80 |
|
| 81 |
4. Tarballs and Build-area directories
|
| 82 |
------------------------------------
|
| 83 |
|
| 84 |
During pkg development before uploaded to debian the tarballs can be found at:
|
| 85 |
|
| 86 |
http://pkg-kde.alioth.debian.org/kde-extra/orig.tar.gz/
|
| 87 |
|
| 88 |
You need to place those dirs in the parent directory of the one from which you're
|
| 89 |
running svn-buildpackage. Usually this means placing tarballs/ and build-area/ dirs
|
| 90 |
in 'pkgname'/ dir, at the same level as trunk/
|
| 91 |
|
| 92 |
If you want to compile inside one version in tags/ dir, you'll need to place those
|
| 93 |
dirs inside that dir. Of course the easiest and cleanest way of doing it is
|
| 94 |
by making a symlink of those dirs inside tags/ dir.
|
| 95 |
|
| 96 |
5. Using svn-inject
|
| 97 |
-------------------
|
| 98 |
|
| 99 |
To inject a new package into the Debian KDE Extras svn archive you should use svn-inject(1)
|
| 100 |
as follows:
|
| 101 |
|
| 102 |
svn-inject -o <package>.dsc svn+ssh://${ALIOTH_USERNAME}@svn.debian.org/svn/pkg-kde/kde-extras
|
| 103 |
|
| 104 |
Type in your alioth password a few hundred times :-) and your package should be
|
| 105 |
uploaded to the archive. Note you will also need to manually copy the
|
| 106 |
package.orig.tar.gz to your tarballs directory. The -o option is important as
|
| 107 |
this ensures that we 'Only keep modified files under SVN control'
|
Parent Directory
| 
Revision Log