--- manuals/trunk/maint-guide/maint-guide.en.dbk 2011/05/03 04:49:01 8787 +++ manuals/trunk/maint-guide/maint-guide.en.dbk 2011/05/03 13:25:47 8791 @@ -869,8 +869,8 @@ Intermediate complexity packages - single binary package, arch = any (executables written in compiled languages such as C and C++) - multiple binary packages, arch = any + all (packages for executables + documentation) + single binary package, arch = any (ELF binary executables compiled from compiler languages such as C and C++) + multiple binary packages, arch = any + all (packages for ELF binary executables + documentation) upstream source in a format other than tar.gz or tar.bz2 upstream source containing undistributable contents @@ -878,8 +878,8 @@ High complexity packages interpreter module package used by other packages - generic library package used by other packages - multiple binary packages including a library package + generic ELF library package used by other packages + multiple binary packages including an ELF library package source package with multiple upstream sources kernel module packages kernel patch packages @@ -1067,8 +1067,8 @@ The second step of the Autotools workflow is usually that the user obtains this distributed source and runs ./configure && make in -the source directory to compile the program into a -binary executable. +the source directory to compile the program into an executable command +binary. Makefile.in -----+ +-> Makefile -----+-> make -> binary @@ -1518,10 +1518,10 @@ $(DESTDIR) to the temporary directory. -For packages of the single binary type, the temporary directory used +For a source package generating a single binary package, the temporary directory used by the dh_auto_install command will be set to debian/package. - For packages of the multiple binary type, the + For a source package generating multiple binary packages, the dh_auto_install command uses debian/tmp as the temporary directory while the dh_install command with the help of @@ -1560,7 +1560,7 @@ options including --prefix=/usr. : -# Where to put binary executables on 'make install'? +# Where to put executable commands on 'make install'? BIN = /usr/local/bin # Where to put icons on 'make install'? ICONS = /usr/local/share/gentoo @@ -1571,7 +1571,7 @@ Debian, so change those paths to: -# Where to put binary executables on 'make install'? +# Where to put executable commands on 'make install'? BIN = $(DESTDIR)/usr/bin # Where to put icons on 'make install'? ICONS = $(DESTDIR)/usr/share/gentoo @@ -1583,7 +1583,7 @@ your package. -So, we should install binary executables in /usr/bin instead of +So, we should install executable commands in /usr/bin instead of /usr/local/bin, the manual page in /usr/share/man/man1 instead of /usr/local/man/man1, and so on. Notice how there's no manual @@ -1629,7 +1629,7 @@ Originally, gentoo's -install target said: +install target said: install: gentoo-target @@ -2141,7 +2141,7 @@ dh_shlibdeps 1 calculates shared library dependencies -for binary packages. It generates a list of ELF executables and shared +for binary packages. It generates a list of ELF executables and shared libraries it has found for each binary package. This list is used for substituting ${shlibs:Depends}. @@ -2407,7 +2407,7 @@ example, debian/rules build and fakeroot make -f debian/rules binary execute rules for build and -binary targets trespectively. +binary targets respectively. Here is a simplified explanation of the targets: @@ -3426,7 +3426,7 @@ src/bar usr/bin -This means when this package is installed, there will be a binary executable +This means when this package is installed, there will be an executable command /usr/bin/bar.