X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=tools.dbk;h=7eeb56704a62541e9322c2bd56ae9748643fd17b;hp=a9b4b816da0f35085f559c3529edcfbd3dfcda43;hb=20ea8ac97f9556ff2f9198d393710f413184d4a8;hpb=cff853d72fc9fcfdc7128189431483d9bd03f1c8 diff --git a/tools.dbk b/tools.dbk index a9b4b81..7eeb567 100644 --- a/tools.dbk +++ b/tools.dbk @@ -26,7 +26,7 @@ exclusion of a competing tool. Most of the descriptions of these packages come from the actual package descriptions themselves. Further information can be found in the package documentation itself. You can also see more info with the command -apt-cache show <package-name>. +apt-cache show package-name.
Core tools @@ -58,7 +58,7 @@ role="package">debconf-doc package. Many feel that this system should be used for all packages which require -interactive configuration; see . . debconf is not currently required by Debian Policy, but that may change in the future. @@ -113,10 +113,10 @@ latest lintian output for the whole development distribution
-<systemitem role="package">debdiff</systemitem> +<command>debdiff</command> debdiff (from the devscripts package, ) +role="package">devscripts package, ) compares file lists and control files of two packages. It is a simple regression test, as it will help you notice if the number of binary packages has changed since the last upload, or if something has changed in the control @@ -175,27 +175,6 @@ them by doing apt-cache search ^dh-.
-
-<systemitem role="package">debmake</systemitem> - -debmake, a precursor to debhelper, is a more coarse-grained -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. - - -The consensus is that debmake is now -deprecated in favor of debhelper. It -is a bug to use debmake in new -packages. New packages using debmake -will be rejected from the archive. - -
-
<systemitem role="package">dh-make</systemitem> @@ -203,7 +182,7 @@ The dh-make package contains dh_make, a program that creates a skeleton of files necessary to build a Debian package out of a source tree. As the name suggests, dh_make is a rewrite of debmake and its template files use dh_* programs +role="package">debmake and its template files use dh_* programs from debhelper. @@ -214,24 +193,6 @@ the package entirely functional and Policy-compliant.
-
-<systemitem role="package">yada</systemitem> - -yada is another packaging helper tool. -It uses a debian/packages file to auto-generate -debian/rules and other necessary files in the -debian/ subdirectory. The -debian/packages file contains instruction to build -packages and there is no need to create any Makefile -files. There is possibility to use macro engine similar to the one used in -SPECS files from RPM source packages. - - -For more informations see YADA site. - -
-
<systemitem role="package">equivs</systemitem> @@ -251,17 +212,17 @@ packages. The following packages help with the package building process, general driving dpkg-buildpackage as well as handling supporting tasks. -
-<systemitem role="package">cvs-buildpackage</systemitem> +
+<systemitem role="package">git-buildpackage</systemitem> -cvs-buildpackage provides the -capability to inject or import Debian source packages into a CVS repository, -build a Debian package from the CVS repository, and helps in integrating +git-buildpackage provides the +capability to inject or import Debian source packages into a Git repository, +build a Debian package from the Git repository, and helps in integrating upstream changes into the repository. -These utilities provide an infrastructure to facilitate the use of CVS by -Debian maintainers. This allows one to keep separate CVS branches of a package +These utilities provide an infrastructure to facilitate the use of Git by +Debian maintainers. This allows one to keep separate Git branches of a package for stable, unstable and possibly experimental distributions, along with the other benefits of a version control system. @@ -293,9 +254,8 @@ package's build-dependencies are correct, and to be sure that unnecessary and wrong build dependencies will not exist in the resulting package. -A related package is pbuilder-uml, -which goes even further by doing the build within a User Mode Linux -environment. +A related package is cowbuilder, +which speeds up the build process using COW filesystem on any standard Linux filesystem.
@@ -342,10 +302,10 @@ signature and checksums before uploading, and the possibility of running
-<systemitem role="package">dcut</systemitem> +<command>dcut</command> -The dcut script (part of the package - ) helps in removing files from the ftp upload directory. +The dcut script (part of the package dput, +) helps in removing files from the ftp upload directory.
@@ -436,10 +396,10 @@ latest entry in a debian/changelog file.
-<systemitem role="package">dpkg-depcheck</systemitem> +<command>dpkg-depcheck</command> dpkg-depcheck (from the devscripts package, ) +role="package">devscripts package, ) runs a command under strace to determine all the packages that were used by the said command. @@ -454,7 +414,9 @@ dpkg-depcheck -b debian/rules build dpkg-depcheck can also be used to check for run-time -dependencies, especially if your package uses exec(2) to run other programs. +dependencies, especially if your package uses +exec 2 +to run other programs. For more information please see