From 24edeec3ea3aef827fc6c23b59bafec1f5343593 Mon Sep 17 00:00:00 2001 From: debacle Date: Wed, 27 Jun 2007 12:57:32 +0000 Subject: [PATCH] Re-applied comments from SGML source to the DocBook files. git-svn-id: svn://anonscm.debian.org/ddp/developers-reference/trunk@4906 313b444b-1b9f-4f58-a734-7bb04f332e8d --- best-pkging-practices.dbk | 48 ++++++++++++++++++++++++++++++++ beyond-pkging.dbk | 7 +++++ l10n.dbk | 1 + new-maintainer.dbk | 7 ++++- pkgs.dbk | 3 ++ resources.dbk | 58 +++++++++++++++++++++++++++++++++++++++ scope.dbk | 1 + tools.dbk | 26 ++++++++++++++++-- 8 files changed, 148 insertions(+), 3 deletions(-) diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk index f1130c2..63b7f87 100644 --- a/best-pkging-practices.dbk +++ b/best-pkging-practices.dbk @@ -142,6 +142,8 @@ the same software but with different configuration options. The vim source package is an example of how to manage this using an hand-crafted debian/rules file. + @@ -318,6 +320,10 @@ implementation? more features? different features? Why should I choose this package. + @@ -601,6 +607,17 @@ NEWS.Debian file in your package. No news is good news! + +
Best practices for maintainer scripts @@ -1303,6 +1320,15 @@ easier, for instance, to keep URLs up to date across multiple files.
Common packaging situations +
Packages using <command>autoconf</command>/<command>automake</command> @@ -1417,9 +1443,30 @@ role="package">common-lisp-controller, about which see /usr/share/doc/common-lisp-controller/README.packaging. +
+ +
Architecture-independent data @@ -1613,6 +1660,7 @@ come from the upstream author(s), or whose contents has been changed by you. would lead to the source failing to build without assistance from the Debian diff, it might be appropriate to instead edit the files, omitting only the non-free parts of them, and/or explain the situation in a README.Debian-source + file in the root of the source tree. But in that case please also urge the upstream author to make the non-free components easier seperable from the rest of the source. diff --git a/beyond-pkging.dbk b/beyond-pkging.dbk index ffbfd3a..f5c7be8 100644 --- a/beyond-pkging.dbk +++ b/beyond-pkging.dbk @@ -171,6 +171,7 @@ given source package via . You can do so by using the <package>@packages.qa.debian.org email address. +
@@ -295,6 +296,12 @@ Sponsoring a package means uploading a package for a maintainer who is not able to do it on their own, a new maintainer applicant. Sponsoring a package also means accepting responsibility for it. + New maintainers usually have certain difficulties creating Debian packages — this is quite understandable. That is why the sponsor is there, to check the diff --git a/l10n.dbk b/l10n.dbk index 76203f3..dec77c4 100644 --- a/l10n.dbk +++ b/l10n.dbk @@ -157,6 +157,7 @@ speakers. The best solution may be to mark the bug as forwarded to upstream, and forward it to both the previous translator and his/her team (using the corresponding debian-l10n-XXX mailing list). +
diff --git a/new-maintainer.dbk b/new-maintainer.dbk index e277466..c52583a 100644 --- a/new-maintainer.dbk +++ b/new-maintainer.dbk @@ -77,7 +77,12 @@ In addition, if you have some packages ready for inclusion in Debian, but are waiting for your new maintainer application to go through, you might be able find a sponsor to upload your package for you. Sponsors are people who are official Debian Developers, and who are willing to criticize and upload your -packages for you. Please read the unofficial debian-mentors FAQ at . +--> +Please read the unofficial debian-mentors FAQ at first. diff --git a/pkgs.dbk b/pkgs.dbk index 68e24f1..5004933 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -812,6 +812,8 @@ outstanding security problems, helping maintainers with security problems or fixing them themselves, sending security advisories, and maintaining security.debian.org. + + When you become aware of a security-related bug in a Debian package, whether or not you are the maintainer, collect pertinent information about the problem, @@ -2262,6 +2264,7 @@ shows build dependencies which are not considered by britney.
out-of-date + For the testing migration script, outdated means: There are different versions in unstable for the release architectures (except for the architectures in fuckedarches; fuckedarches is a list of architectures that don't keep up (in diff --git a/resources.dbk b/resources.dbk index a167915..cc04f3d 100644 --- a/resources.dbk +++ b/resources.dbk @@ -337,6 +337,7 @@ questions.
The CVS server + Our CVS server is located on cvs.debian.org. @@ -950,6 +951,63 @@ announcement will be posted to Though ftp-master is restricted, a copy of the installation is available to all developers on merkel.debian.org. +
diff --git a/scope.dbk b/scope.dbk index 5e706c2..d4788a6 100644 --- a/scope.dbk +++ b/scope.dbk @@ -7,6 +7,7 @@ The purpose of this document is to provide an overview of the recommended procedures and the available resources for Debian developers. + The procedures discussed within include how to become a maintainer ( ); how to create new packages (
- + - -- 2.30.2