> Can I still get source tarballs and compile under Redhat? Does the
>"configure/make/make install" still work? Is there compatibility problems
>between "non-redhat" programs (i.e. source tarballs rather than .rpm) and
>glibc, etc? What if I want/need to install "non-Redhat" libraries?
Yes, you can do all that under RedHat (in fact, I do, mostly because
the people that make RPMs don't put them where I want them to go!).
There are no compatibility problems. If you want to ignore the packaging
system after installation, go right ahead -- it'll behave just like your
old slackware system (except everyhing will be in the right place :-)
> I'm assuming that if I install some stuff as source, it ruins the rpm
>database (in terms of dependancies, etc.). Is this correct?
Yes, but only for those things that conflict with already installed
packages.
> Or is a less user-friendly package like Slackware or Debian still a
>better choice for us renegades?
My advice would be to go with RedHat or Debian. I prefer RedHat,
and much of it's personal choice -- I just find RedHat easier to
configure and maintain in the long run. Debian had (still has?
I haven't checked 2.0) dselect, which was great, but it could
as easily sat on top of RPM as on yet another packaging format
(.deb). dpkg has apparently been replaced by apt in the latest
Debian, but I haven't looked at that.
Tet
--
Politicians should read SF, not westerns and detective stories. - A.C.Clarke
--------------------+--------------+----------------------------------------
[EMAIL PROTECTED] | Micro$oft: | Linux, the choice of a GNU generation.
[EMAIL PROTECTED] | Just say no! | See http://www.uk.linux.org for details
