[Pkg-freedict-commits] r108 - /packages/freedict-deu-tur/trunk/debian/README

[kebil-guest at users.alioth.debian.org]

Author: kebil-guest
Date: Mon Jan 22 22:31:43 2007
New Revision: 108

URL: http://svn.debian.org/wsvn/pkg-freedict/?sc=1&rev=108
Log:
Changed README file

Modified:
    packages/freedict-deu-tur/trunk/debian/README

Modified: packages/freedict-deu-tur/trunk/debian/README
URL: http://svn.debian.org/wsvn/pkg-freedict/packages/freedict-deu-tur/trunk/debian/README?rev=108&op=diff
==============================================================================
--- packages/freedict-deu-tur/trunk/debian/README (original)
+++ packages/freedict-deu-tur/trunk/debian/README Mon Jan 22 22:31:43 2007
@@ -1,59 +1,2 @@
-Convenience targets in debian/rules
-===================================
-The debian/rules file supports several targets that are not required by Debian
-Policy. This include:
-
-  debian/rules prepare              Sets up the package build directory
-                                    structure as quilt expects to find it.
-  debian/rules patch                Applies all patches to the source tree.
-  debian/rules unpatch              Reverts all patches from the source tree.
-
-
-Editing and creating patches
-============================
-To start, you should be in the source package directory -- this is the
-directory that contains the debian/ directory.  Run "debian/rules prepare";
-this will set up the proper symlinks so that quilt can find the patches it
-needs to apply.  Once this is done, you will see a symlink named "patches"
-that will point to debian/patches. This exists because quilt expects the
-patches directory to be located at the top level by default. The "prepare"
-target sets up a ".pc" directory as well, which quilt uses internally to
-store information it needs.
-
-What you do next depends on whether you want to edit an existing patch, or
-create a new one.
-
-Editing an existing patch
--------------------------
-Run "quilt push yourpatchname.diff".  Make your edits now, directly in the
-source tree.  If you're editing a file that wasn't previously included in the
-patch, you must let quilt know you're doing it by using "quilt add" or "quilt
-edit".  If you're not sure if you need this, you can run "quilt files" to see
-if your file is already in there, or "quilt patches filename" to see if the
-current patch edits the specified file.  Once you're done editing, run "quilt
-refresh" to update your patch.  All documentation in the patch header will be
-retained by quilt automatically.  Always document the changes you have made in
-the header of the patch.
-
-Creating a new patch
---------------------
-Decide where your patch belongs according to the number series. Once you do
-this, run "quilt push patch-before-yours", where "patch-before-yours" specifies
-the filename of the patch that will be the last one applied before your new
-patch. Then run "quilt new patchname" using the name of the patch (including
-the appropriate number). Make your edits to the source files, directly in the
-source tree.  As described above in the case of editing existing patches,
-you'll want to be sure quilt knows which files you are editing.  When you are
-finished, run "quilt refresh -u -p 0".  This will create a unified diff patch
-with a strip number of 0.  You should then go in to the patches directory and
-document your patch by adding a description of it to the top of the patch file.
-
-You may have a patch that you stole from some other source that you just want
-to apply and you don't want to deal with adding files by hand.  You can use
-"quilt import -n internal-patch-name file-name" where "internal-patch-name"
-is what you want to call your patch.  You'll want to "quilt push" the patch
-before yours -- as described above -- before doing the import, to ensure that
-that it applies in correct sequence.
-
-Once you're all done with patch creation/editing, run "debian/rules clean" to
-get rid of the things that had to be set up.
+About editing and creating the patches for this package see
+/usr/share/doc/freedict-tools-dev/README.devel