From 00fe222417a611199dd5d523caeb06b0a70d1040 Mon Sep 17 00:00:00 2001 From: aph Date: Sun, 1 Nov 1998 22:27:09 +0000 Subject: [PATCH] use new tag where appropriate (Ardo, you rock) advise against uploading when a package has lintian problems of severity 'E' rename 'Whirlwind Tour' section to 'Overview of...' git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@683 313b444b-1b9f-4f58-a734-7bb04f332e8d --- developers-reference.sgml | 108 +++++++++++++++++++------------------- 1 file changed, 55 insertions(+), 53 deletions(-) diff --git a/developers-reference.sgml b/developers-reference.sgml index 276f811..867204b 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -78,7 +78,7 @@ Manual">. Getting started

So, you've read all the documentation, you understand what everything -in the pgp underway) for the database of keys which is distributed from /pub/debian/doc/debian-keyring.tar.gz, or the -debian-keyring package). Please be sure to sign your + Once this information is received and processed, you should be @@ -241,7 +241,7 @@ unsubscribe to the mailing lists can be found at , or locally in /usr/doc/debian/mailing-lists.txt if you have the -doc-debian package installed. +doc-debian package installed.

When replying to messages on the mailing list, please do not send a carbon copy ( The first time a version is uploaded which corresponds to a particular upstream version the original source tar file should be uploaded and @@ -693,25 +692,29 @@ Before you upload your package, you should do basic testing on it. Make sure you try the following activities (you'll need to have an older version of the Debian package around). - install the package and make sure the software - works, or upgrade the package from an older version to - your new version if a Debian package for it already - exists - - downgrade the package to the previous version - (if one exists) -- this tests the remove the package - - run lintian -v - package-NN.changes. This will check the - source package as well as the binary package. If you - don't understand the output that +Install the package and make sure the software works, or upgrade the +package from an older version to your new version if a Debian package +for it already exists. + + +Run lintian -v package-NN.changes. This will +check the source package as well as the binary package. If you don't +understand the output that +Normally, a package should +For more information on . + +Downgrade the package to the previous version (if one exists) -- this +tests the +Remove the package, then reinstall it. @@ -735,7 +738,7 @@ of such software should go to -You may also find the Debian package for details). Carefully examine the installation log sent to you when the package is installed into the archive. If for some reason the old location of the package remains, file a bug against - If for some reason you want to completely remove a package (say, if it is an old compatibility library which is not longer required), you -need to file a bug against @@ -972,7 +975,7 @@ obsolete name of the package (see the for details). Once you've uploaded that package, and the package has moved into the archive, file a bug -against , or, if you have -installed the /usr/doc/debian/bug-*.

Often as a package maintainer, you find bugs in other packages or else @@ -1030,13 +1033,13 @@ number. Lintian reports

-You should periodically get the new . That report, which is updated automatically, contains Reporting lots of bugs at once @@ -1054,70 +1057,69 @@ send the bug report to Whirlwind Tour of Debian Maintainer Tools + Overview of Debian Maintainer Tools

This section contains a rough overview of the tools available to maintainers. These tools are meant to help convenience developers and free their time for critical tasks.

Some people prefer to use high-level package maintenance tools and -some do not. Debian is officially agnostic on this issue, other than -making the attempt to accommodate the reasonable wishes of developers. -Therefore, this section is not meant to stipulate to anyone which -tools they should use or how they should go about with their duties of -maintainership. Nor is it meant to endorse any particular tool to the -exclusion of a competing tool. +some do not. Debian is officially agnostic on this issue; any tool +which gets the job done is fine. Therefore, this section is not meant +to stipulate to anyone which tools they should use or how they should +go about with their duties of maintainership. Nor is it meant to +endorse any particular tool to the exclusion of a competing tool.

Most of the descriptions of these packages come from the actual package descriptions themselves. - dpkg-dev + -dpkg-dev contains the tools (including + - lintian + -Lintian dissects Debian packages and reports bugs and +lintian has already been discussed in and . - debhelper + -debhelper is a collection of programs that can be used in +debian/rules to automate common tasks related to building binary Debian packages. Programs are included to install various files into your package, compress files, fix file permissions, integrate your package with the Debian menu system.

-Unlike debmake, debhelper is broken into +Unlike debmake. + - debmake + -debmake, a pre-cursor to debhelper, is a +debian/rules assistant. It includes two main programs: deb-make, which can be used to help a maintainer convert a regular (non-Debian) source archive into a Debian source package; and debstd, which incorporates in one big shot the same sort of automated functions that one finds in -debhelper. + - cvs-buildpackage + -cvs-buildpackage provides the capability to inject or + - dupload + -dupload is a package and a script to automagically upload +