path: root/ubuntu/maverick/applications/kmplayer/debian/README.Debian
diff options
authorMichele Calgaro <>2019-04-03 22:56:40 +0900
committerMichele Calgaro <>2019-04-03 22:56:40 +0900
commit11394aecd1f906fee2ebd2b90412aeba4651fbff (patch)
treebcf750380e6d9fc7dbe524e16bbe2afde25dcfa0 /ubuntu/maverick/applications/kmplayer/debian/README.Debian
parentd24bd898174453b586ac90f2ef7a60165fa26fde (diff)
DEB: use _base folder for a distro instead of specific distros (squeeze
and maverick). Signed-off-by: Michele Calgaro <>
Diffstat (limited to 'ubuntu/maverick/applications/kmplayer/debian/README.Debian')
1 files changed, 0 insertions, 107 deletions
diff --git a/ubuntu/maverick/applications/kmplayer/debian/README.Debian b/ubuntu/maverick/applications/kmplayer/debian/README.Debian
deleted file mode 100644
index b0302c211..000000000
--- a/ubuntu/maverick/applications/kmplayer/debian/README.Debian
+++ /dev/null
@@ -1,107 +0,0 @@
-Debian kde-extras Team
-1. Contacts
-General help requests
- <> mailing list
- #debian-kde on irc
-Packaging queries
- <> mailing list
- #debian-qt-kde on irc
- <> mailing list
-2. Subversion repository
-You can browse it only at:
-To "checkout" the repository use these commands:
- $ svn co svn+ssh://${ALIOTH_USERNAME}
-Authorized SSH keys are controlled at
-The repository layout is:
-- packagename/
-    - trunk/
-    - branches/
-    - tags/
-        - 0.7.2-1/
-        - 0.7.2-2/
-        - 0.7.2-2ubuntu1/
-        - 0.7.2-2ubuntu2/
-        - 0.7.2-2ubuntu3/
-        - 0.8.0/
-        ...
-If only one version of the package is available at the time, development must
-be made at trunk/ dir, copying the dir to tags/'pkg-version' each time a new
-release is made.
-When, at some point, the need to have two different versions at the same time
-arises (for example, if we need a version to be in unstable and a different one
-to be in experimental), experimental development will be made in trunk/ and
-if a new unstable package needs to be cooked, copying
-tag/'latest_version_in_sid' to tag/'latest_version_in_sid'+1 will make the
-3. Using svn-buildpackage
-Packages with an upstream tarball will require you to set the mergeWithUpstream
-property first (from the package root) so that svn-buildpackage will look for
-the .orig.tar.gz in the ../tarballs directory.
- % svn propset mergeWithUpstream 1 debian
-Please note that this only works for packages which have only the debian/
-directory committed. Consequently, you must use CDBS's or
-dpatch to modify the upstream sources.
-After you have finished and committed your Debian patches via
- % svn commit [PACKAGE]
-as well as copying the orig.tar.gz to ../tarballs/ if necessary, you may build
-your package with the following commands:
- % svn-buildpackage --svn-ignore-new -rfakeroot
-Please, don't commit tarballs/ or build-area/ directories to SVN.
-4. Tarballs and Build-area directories
-During pkg development before uploaded to debian the tarballs can be found at:
-You need to place those dirs in the parent directory of the one from which you're
-running svn-buildpackage. Usually this means placing tarballs/ and build-area/ dirs
-in 'pkgname'/ dir, at the same level as trunk/
-If you want to compile inside one version in tags/ dir, you'll need to place those
-dirs inside that dir. Of course the easiest and cleanest way of doing it is
-by making a symlink of those dirs inside tags/ dir.
-5. Using svn-inject
-To inject a new package into the Debian KDE Extras svn archive you should use svn-inject(1)
-as follows:
- svn-inject -o <package>.dsc svn+ssh://${ALIOTH_USERNAME}
-Type in your alioth password a few hundred times :-) and your package should be
-uploaded to the archive. Note you will also need to manually copy the
-package.orig.tar.gz to your tarballs directory. The -o option is important as
-this ensures that we 'Only keep modified files under SVN control'