I can't say whether this is the "best" way, but here's what I did:

1. Starting with a reasonably fresh install of 7.2...

2. From the URL in the announcement message, download all the RPMS. Put them 
in a directory.

3. Create a subdirectory called "libical" and move the libical RPMs into it.

4. Create a subdirectory called "printing" amd move the following RPMs into 
it:
        cups-1.1.4-9mdk.i586.rpm
        cups-common-1.1.4-9mdk.i586.rpm
        cups-drivers-1.0-2.1mdk.i586.rpm
        ghostscript-5.50-48mdk.i586.rpm
        ghostscript-module-SVGALIB-5.50-48mdk.i586.rpm
        ghostscript-module-X-5.50-48mdk.i586.rpm
        ghostscript-utils-5.50-48mdk.i586.rpm
        kups-0.8-27.1mdk.i586.rpm
        kups-devel-0.8-27.1mdk.i586.rpm
        libcups1-1.1.4-9mdk.i586.rpm
        libcups1-devel-1.1.4-9mdk.i586.rpm
        libqtcups1-1.1-2.1mdk.i586.rpm
        libqtcups1-devel-1.1-2.1mdk.i586.rpm
        qtcups-1.1-2.1mdk.i586.rpm

5. Starting in the "libical" directory...

        rpm -ivh libical-0.20d-2mdk.i586.rpm 

6. In the parent directory (containing the remaining RPMs) enter:

        rpm --rebuild
        rpm -Uvh *.rpm --test

The --test will tell you whether proceeding with the install is likely to 
encounter any problems. Assuming it doesn't...

        rpm -Uvh *.rpm
        rpm --rebuilddb
        update-menus -v

7. In the "printing" directory...

        rpm -Uvh *.rpm
        rpm --rebuilddb
        update-menus -v

I split out the printing stuff so as not to lump everything into one massive 
update. (I also rebuild the RPM database frequently because I've had problems 
updating too many RPMs at once.) There seem to be two versions of libical in 
the most recent update. I only installed the second one noted above. (It 
needed to be installed before the remaining RPMS in the parent directory.)

This may not be the best approach -- but it worked for me. 

Cheers.

M.

On Tuesday 02 January 2001 15:21, you wrote:
> All I have now is 33 rpm files in a dir and I have no idea what
> to do next.. when I try to unpack a file it says it can't because
> it depends on another file.. I'm really confused here :)
>
> -Johan-

-- 
Michael O'Henly
TENZO Design

Reply via email to