pan-users
[Top][All Lists]
Advanced

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

[Pan-users] Re: 'Old' Pan for PCLinuxOS?


From: Duncan
Subject: [Pan-users] Re: 'Old' Pan for PCLinuxOS?
Date: Fri, 15 Feb 2008 18:23:15 +0000 (UTC)
User-agent: Pan/0.132 (Waxed in Black)

Maurice <address@hidden> posted
address@hidden, excerpted below, on  Fri, 15 Feb
2008 17:29:29 +0000:

> Anyhow, I've now found that what I needed on PCLInuxOS to install the
> RPMs was KPackage.

Interesting.  So all you needed was an rpm handler?  I thought pclinuxos 
was based on mandr(ake|iva), and thus rpm based already, and that it 
followed that it had rpm handling built-in?  Is that incorrect?

Or maybe you just didn't know how to use the CLI rpm command and needed a 
point and click GUI.  I should have thought of that, but even back on 
Mandrake, I used both the GUI and CLI interfaces with pretty much equal 
ease.  Of course, that was largely due to the great intro to the CLI rpm 
command as found in O'Reilly's Linux in a Nutshell (Linux/NS), one of two 
very great books I had multiple recommendations for after asking for book 
recommendations, when I decided I had to get serious about Linux.  (BTW, 
the other was Running Linux (RL).  I got both, even purchasing a newer 
edition of Linux/NS later -- all three were very well used!  Linux/NS is 
mostly quick-ref, but has a number of appendices in the back for more 
complex commands, while RL is more textbook style, simple/basic stuff in 
front, more advanced stuff as one advances thru the book. Both are 
EXTREMELY good books for Linux beginners.  Together they cost me ~$75, 
probably closer to $90 today, but saved me, I figure, at minimum 500 
hours of "messing around" trying to learn stuff.  That's three months 40-
hour/wk full-time equivalent; consider what your time is worth and do the 
math on what sort of value these books can be.)

Anyway, what I expected was wrong was that the rpm was listing 
dependencies that your distribution had, but called something slightly 
different, so the dependencies couldn't be resolved automatically.  If 
kpackage handled it, evidently they were resolved automatically, and it 
was more a problem of knowing what tools to use or how.

So glad it worked, and thanks for the report on what fixed it, so I or 
others can hopefully better help the next guy. =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman





reply via email to

[Prev in Thread] Current Thread [Next in Thread]