diff from 2260 and 21737

Description: Circumvent Debian package dependencies
 This package provides a tool to create Debian
 packages that only contain dependency information.
 .
 If a package P is not installed on the system, packages
 that depend on P cannot normally be installed.  However,
 if equivalent functionality to P is known to be installed,
 this tool can be used to trick the Debian package management
 system into believing that package P is actually installed.
 .
 Another possibility is creation of a meta package. When this
 package contains a dependency as "Depends: a, b, c", then
 installing this package will also select packages a, b and c.
 Instead of "Depends", you can also use "Recommends:" or
 "Suggests:" for less demanding dependency.
 .
 Please note that this is a crude hack and if thoughtlessly used,
 it might possibly do damage to your packaging system. And please
 note as well that using it is not the recommended way of dealing
 with broken dependencies. Better file a bug report instead.

Description: Circumvent Debian package dependencies
 This package provides a tool to create Debian packages that only
 contain dependency information.
 .
 One use for this is to create a metapackage: a package whose sole
 purpose is to declare dependencies and conflicts on other packages so
 that these will be automatically installed, upgraded, or removed.
 .
 Another use is to circumvent dependency checking.  If a package P is
 not installed on the system, packages that depend on P cannot normally
 be installed.  However, if functionality equivalent to P is known to
 be installed, this tool can be used to trick the Debian package
 management system into believing that package P is actually installed.
 NOTE: this should be considered a crude hack to work around awkward
 situations, not a normal solution.  If you use equivs to work around
 bugs in other Debian packages, you should also file bug reports
 against those packages.

--- 2260	Thu Jan  1 00:00:00 1970
+++ 21737	Thu Jan  1 00:00:00 1970
@@ -1,20 +1,17 @@
 Circumvent Debian package dependencies
- This package provides a tool to create Debian
- packages that only contain dependency information.
+ This package provides a tool to create Debian packages that only
+ contain dependency information.
  .
- If a package P is not installed on the system, packages
- that depend on P cannot normally be installed.  However,
- if equivalent functionality to P is known to be installed,
- this tool can be used to trick the Debian package management
- system into believing that package P is actually installed.
+ One use for this is to create a metapackage: a package whose sole
+ purpose is to declare dependencies and conflicts on other packages so
+ that these will be automatically installed, upgraded, or removed.
  .
- Another possibility is creation of a meta package. When this
+ Another use is to circumvent dependency checking.  If a package P is
- package contains a dependency as "Depends: a, b, c", then
+ not installed on the system, packages that depend on P cannot normally
- installing this package will also select packages a, b and c.
+ be installed.  However, if functionality equivalent to P is known to
- Instead of "Depends", you can also use "Recommends:" or
+ be installed, this tool can be used to trick the Debian package
- "Suggests:" for less demanding dependency.
+ management system into believing that package P is actually installed.
- .
+ NOTE: this should be considered a crude hack to work around awkward
- Please note that this is a crude hack and if thoughtlessly used,
+ situations, not a normal solution.  If you use equivs to work around
- it might possibly do damage to your packaging system. And please
+ bugs in other Debian packages, you should also file bug reports
- note as well that using it is not the recommended way of dealing
+ against those packages.
- with broken dependencies. Better file a bug report instead.