[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [jakemsr@clipper.net: Re: lie to apt]



Previously Jacob Meuser wrote:
> ----- Forwarded message from Jacob Meuser <jakemsr@clipper.net> -----
> On Wed, Feb 21, 2001 at 06:16:22PM -0500, xsdg wrote:
> > On Wed, Feb 21, 2001 at 10:13:23AM +0000, Jacob Meuser wrote:
> > > Is there a way to manually edit the database that says which packages
> > > are installed?

Of course you can, but it is strongly advised not to do that. I suggest
you look at the equivs package instead:

Package: equivs
Priority: extra
Section: admin
Installed-Size: 50
Maintainer: Martin Bialasinski <martinb@debian.org>
Architecture: all
Version: 2.0.2
Depends: perl | perl5, debhelper, dpkg-dev, devscripts, make, fakeroot
Filename: pool/main/e/equivs/equivs_2.0.2_all.deb
Size: 17394
MD5sum: 0c84d50f864ea181738fc1b496b6fb20
Description: Circumventing Debian package dependencies
 This is a dummy package which can be used to create Debian
 packages, which only contain dependency information.
 .
 This way, you can make the Debian package management
 system believe that equivalents to packages on which other
 packages do depend on are 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
 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.

Wichert.

-- 
  _________________________________________________________________
 /       Nothing is fool-proof to a sufficiently talented fool     \
| wichert@cistron.nl                  http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |



Reply to: