Dts12: 5.4 release synchronisation

2006-12-28T18:20:32Z

5.4 release synchronisation

Dts12 at 22:23, 21 October 2006

2006-10-21T22:23:19Z

New page

This has been particularly noted on RedHat 9, complaining about the
module <CODE>"perl(Term::ReadKey)"</CODE> - even if this is actually present (e.g.
having been installed directly from CPAN). In fact, this is not
specific to perl modules - the same issue can potentially arise with
other RPM dependencies.

The problem is that the RPM mechanism keeps a local database of what
software packages have been installed, and checks this for any other
features that this RPM requires. If software is installed "manually"
rather than via rpm packages, then it will not appear in this database.
Attempting to install another RPM that rely on this functionality will
then complain about the "missing" package, because the RPM system doesn't
know that's it's actually available.

The ideal solution is to '''always''' install software using a consistent
mechanism (which may involve building RPMs locally, or looking for a
suitable pre-built version).

Failing this, it's possible to tell the <CODE>"rpm"</CODE> command to ignore such
dependencies, and install the package anyway. Try:

rpm -i --nodeps {package}

In this situation, it's then up to you to make sure that any other
necessary packages '''are''' actually present on the system.

@@ Line 1: / Line 1: @@
 This has been particularly noted on RedHat 9, complaining about the
 module <CODE>"perl(Term::ReadKey)"</CODE> - even if this is actually present (e.g.
 having been installed directly from CPAN).  In fact, this is not
-specific to perl modules - the same issue can potentially arise with
+specific to Perl modules - the same issue can potentially arise with
 other RPM dependencies.

Template:FAQ:Perl 09 - Revision history

Dts12: 5.4 release synchronisation

Dts12 at 22:23, 21 October 2006