Re: [TCLUG:15263] Reading Red Hat rpms vs deb

[Tim Neu <tim@tneu.visi.com>]

On Tue, 28 Mar 2000, Callum Lerwick wrote:

> > For example, if you install both the acroread and netscape rpm files, you
> > have to programs - acrobat & netscape.   Both do not interoperate without
> > additional configuration.. (besides perhaps adding a .pdf mime type).
> >
> > On debian, the acrobat reader .deb file sees that netscape is installed,
> > and sets itself up automatically as a netscape plugin (so you can view PDF
> > files inline in your browser).  Same thing with RealAudio player (in the
> > unstable tree, at least).  This is just one example; however in general
> > the package system is much smarter in debian.
> 
> What if you install acroread before netscape?

I've never tried it, is the honest answer.  However, I know for sure you
could (hypotheicaly) do an apt-get remove acroread, then apt-get install
acroread and have it do the right thing.   I think it depends on the
package maintainer.   In this case, the acroread package maintainer went
through the extra work to get it to integrate properly.  If netscape's
package maintainer did the same thing, then it would work both
ways.  (actually, I do not know that it doesn't, I just have never tried
it). 

> > 1.  Debian's package managment system is smart enough to do an ENTIRE
> > UPGRADE from an old version of debian to a newer version online (without
> > re-installing).
> 
> Without rebooting? Then you'd have something. Otherwise RedHat does it

Unless you upgrade the kernel package, you do not have to reboot to
upgrade to a new Debian.  Plus, you can do the entire upgrade via FTP from
a local mirror.  (no need to order a CD, boot from a floppy, etc). 

In the case of major architectual changes (i.e. moving from libc5 to
glibc) a reboot is recommended but not required. 

> > 2.  Debian's package managment system allows you to, for example, point to
> > the stable package tree for your whole system, then only upgrade packages
> > of your choosing.
> 
> Redhat will let you choose which packages to upgrade during a dist
> upgrade.

Could very well be!  I have only used 5.2 & 6.0; however, I have seen
NUMEROUS occurances where redhat is unable to resolve dependancy
problems.  Sure, RPM does tell you that package X needs package Y; but if
it cannot find package Y you're screwed. 

I guess it is dificult to quantify, since both DEB & RPM have the similar
features (dependancy resolution vs dependancy checking).  I can say that I
have had numerous occasions where Redhat could not install something
because it couldn't find a dependancy, and I have yet to see a single
instance (in the stable tree) where Debian has failed to handle and
install dependancies correctly (in the correct order, etc).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
______         _ __         "If you don't have the freedom to use what you
  /           ' )  )               own - then you do not own anything."    
 / o ______    /  / _  . .    No apologies to Jack Valenti or the MPAA
/ <_/ / / <   /  (_</_(_/_  -- tneu@visi.com / http://www.visi.com/~tneu --