For sure. The only thing I'd make sure of is that I ./configure
--prefix=/usr/local/thing-i-am-installing as to not stomp on redhat's
nicely managed packages.
Heck, make a .spec file to compile things, and you can manage everything
as packages still.
-----------------------------------------------------------------------------
/\ Joe Hohertz - Senior Systems Administrator
/ \ [EMAIL PROTECTED] http://www.golden.net/~jhohertz
/____\
-----[The opinions expressed by me do not necessarily match those of GT]-----
On Tue, 17 Nov 1998, Lloyd Sumpter wrote:
>
> I don't want to start a "package war", but I'm thinking of switching
> from Slackware to Redhat. I don't give a fig about "ease of installation"
> - I've been installing Linux from 0.97. In fact, my concern is that Redhat
> won't let me remain "independant".
> 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?
> I'm assuming that if I install some stuff as source, it ruins the rpm
> database (in terms of dependancies, etc.). Is this correct?
>
> Or is a less user-friendly package like Slackware or Debian still a
> better choice for us renegades?
>
> =======================================================================
> Lloyd Sumpter E-MAIL: [EMAIL PROTECTED]
> Protection and Control Design or: [EMAIL PROTECTED]
> BC Hydro, Vancouver, CANADA PHONE: (604) 528-3078
> "organizing Pagans is like herding cats"
>
