Differences between revisions 13 and 14
Revision 13 as of 2009-01-04 15:48:57
Size: 2428
Editor: FranklinPiat
Comment: Fix link
Revision 14 as of 2009-03-16 03:31:34
Size: 2438
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * [http://groups.google.com/group/linux.debian.bugs.dist/topics Search Debian bug reports]  * [[http://groups.google.com/group/linux.debian.bugs.dist/topics|Search Debian bug reports]]
Line 7: Line 7:
 * One of the most common new-Debian-user mistakes involves forcing packages to install. Do '''not''' do this unless you know exactly how it affects everything else. Instead, research the problem first (ie., search the archives at [http://lists.debian.org lists.debian.org]), and if you can't find a solution, ask in debian-*@lists.debian.org (try debian-user first if there's no better list related to your problem). Do not install an application from source tarballs (blah.tar.gz or .tgz) expecting Debian packages to use it properly (use deb-src packages instead, or dump it into /usr/local). Debian packages often have Debian-specific bits; packages that depend on other packages will likely depend on the Debian-specific bits as well.  * One of the most common new-Debian-user mistakes involves forcing packages to install. Do '''not''' do this unless you know exactly how it affects everything else. Instead, research the problem first (ie., search the archives at [[http://lists.debian.org|lists.debian.org]]), and if you can't find a solution, ask in debian-*@lists.debian.org (try debian-user first if there's no better list related to your problem). Do not install an application from source tarballs (blah.tar.gz or .tgz) expecting Debian packages to use it properly (use deb-src packages instead, or dump it into /usr/local). Debian packages often have Debian-specific bits; packages that depend on other packages will likely depend on the Debian-specific bits as well.
Line 15: Line 15:
 * Consider building a Debian package of the program. You don't need to be a Debian Developer to port packages to Debian (but you will need to learn about non-maintainer uploads; see [http://www.debian.org/doc/packaging-manuals/developers-reference/ Developer's Reference], section 5.11).  * Consider building a Debian package of the program. You don't need to be a Debian Developer to port packages to Debian (but you will need to learn about non-maintainer uploads; see [[http://www.debian.org/doc/packaging-manuals/developers-reference/|Developer's Reference]], section 5.11).
Line 27: Line 27:
 * [http://www.debian.org/doc/manuals/reference/ch-tips Debian tips in the manual]
 * [http://dabase.com/tips/ dabase Debian tips]
 * [[http://www.debian.org/doc/manuals/reference/ch-tips|Debian tips in the manual]]
 * [[http://dabase.com/tips/|dabase Debian tips]]

First step is search


Do not force Debian Package Management

  • One of the most common new-Debian-user mistakes involves forcing packages to install. Do not do this unless you know exactly how it affects everything else. Instead, research the problem first (ie., search the archives at lists.debian.org), and if you can't find a solution, ask in debian-*@lists.debian.org (try debian-user first if there's no better list related to your problem). Do not install an application from source tarballs (blah.tar.gz or .tgz) expecting Debian packages to use it properly (use deb-src packages instead, or dump it into /usr/local). Debian packages often have Debian-specific bits; packages that depend on other packages will likely depend on the Debian-specific bits as well.

  • Installing a program from source into /usr/local is encouraged, so long as no Debian packages depend on that program, and it doesn't mess with anything outside /usr/local. The packaging system pretty much ignores /usr/local, by design.
  • When installing a program from source into /usr/local, consider using stow or checkinstall.
  • If you really want to install a program from source, but other Debian packages depend on that program, have a look at the 'equivs' package.
  • Consider building a Debian package of the program. You don't need to be a Debian Developer to port packages to Debian (but you will need to learn about non-maintainer uploads; see Developer's Reference, section 5.11).

  • Use apt-get, aptitude, synaptic, dselect, or another dpkg frontend. dpkg itself should be reserved for admins who are familiar with Debian installations (and know how to climb out of holes they've dug themselves into).
  • If you do mess with package management, don't expect any of the package managemet tools to work any more :( Debian is very sensitive to its package database being up-to-date and correct.

Tips are sub-categorized as follows;

External tips