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