CleanupDebianPackages - Versionsgeschichte

imported>Ms: /* Solution */

2009-09-12T08:22:35Z

Solution

← Nächstältere Version		Version vom 08:22, 12. Sep 2009
Zeile 13:		Zeile 13:
	Create a meta package (ubuntu-meta is a good start) with a lengthy dependency list.		Create a meta package (ubuntu-meta is a good start) with a lengthy dependency list.
	./debian/rules binary		./debian/rules binary

			Prerequisite for building packages
			apt-get install debhelper dh-make

	The ubuntu/kubuntu meta package can be obtained with ''apt-get source ...''.		The ubuntu/kubuntu meta package can be obtained with ''apt-get source ...''.

Admin: 4 Version(en)

2008-01-09T19:27:42Z

4 Version(en)

← Nächstältere Version

Version vom 19:27, 9. Jan 2008

imported>Ms: /* Solution */

2006-04-02T13:06:03Z

Solution

← Nächstältere Version		Version vom 13:06, 2. Apr 2006
Zeile 13:		Zeile 13:
	Create a meta package (ubuntu-meta is a good start) with a lengthy dependency list.		Create a meta package (ubuntu-meta is a good start) with a lengthy dependency list.
	./debian/rules binary		./debian/rules binary

			The ubuntu/kubuntu meta package can be obtained with ''apt-get source ...''.

	Install that package and make it sticky:		Install that package and make it sticky:
			apt-get install deborphan ms-desasterarea
	sudo deborphan -A ms-desasterarea		sudo deborphan -A ms-desasterarea

	Search for orphaned packages:		Search for orphaned packages:
	deborphan -a \| sort -k2,2		deborphan -a \|grep -vE "^main/libdevel" \| sort -k2,2

			Development packages can be kept. Unwanted library packages can be deleted on a general basis:
			apt-get --purge remove `deborphan`

			Run that command several times till no orphaned library package is left.

	Any unwanted und not via dependency required package can be removed with ''apt-get --purge remove ...''.		Any unwanted und not via dependency required package can be removed with ''apt-get --purge remove ...''.

imported>Ms: /* Solution */

2006-02-05T17:22:32Z

Solution

← Nächstältere Version		Version vom 17:22, 5. Feb 2006
Zeile 19:		Zeile 19:
	Search for orphaned packages:		Search for orphaned packages:
	deborphan -a \| sort -k2,2		deborphan -a \| sort -k2,2

			Any unwanted und not via dependency required package can be removed with ''apt-get --purge remove ...''.
			After iterating that several times deborphan only returns development packages (that I do not include in my meta package).

	==Filesystem Layout==		==Filesystem Layout==

imported>Ms: added file contents

2006-02-05T16:07:12Z

added file contents

@@ Zeile 12: / Zeile 12: @@
 Create a meta package (ubuntu-meta is a good start) with a lengthy dependency list.
-Make that package sticky:
+  ./debian/rules binary
    sudo deborphan -A ms-desasterarea
 Search for orphaned packages:
    deborphan -a | sort -k2,2

imported>Ms: initial draft

2006-02-05T15:35:07Z

initial draft

Neue Seite

==The Problem==
The number of installed packages tends to grow on a debian system (like with any other distribution and operating system).
Packages are installed, dependent packages are installed, too.
It becomes difficult to decide, which packages are really wanted.

Some people suggest the usage of aptitude since it keeps the information, if a package was installed on unser request or as a result of a dependency.

==Solution==
The deborphan tool lists any package that is not required by at least one other package.

So having a private meta package just containing dependencies and running deborphan helps.

Create a meta package (ubuntu-meta is a good start) with a lengthy dependency list.
Make that package sticky:
sudo deborphan -A ms-desasterarea

Search for orphaned packages:
deborphan -a | sort -k2,2