On Thu, Mar 02, 2000 at 11:48:22AM +1100, Chuck Dale wrote:
> But have you noticed that it is not RPM which is doing any of the
> compiling of the source code? Ok so it runs configure and make for you
> but that is about it. It doesn't do any checking on your system to find
> dependies as the original poster was saying configure does.
Errrm, there seem to be slight mix-ups around... :-)
a) not all programs out there actually *have* configure. Many still use
their own way of configuring things or use imake/xmkmf to do so. The
latter depends very much on the operator of the machine having set up
the congiuration files for imake correctly (which fortunately seems
to be the case under Red Hat).
b) When (re)building an RPM of an application which *does* use
configure, rpm will run configure just as if you had run it from the
commandline. Hence, all the checks the configure script performs will
be performed and rpm will fail should the configure script fail (due
to missing libraries, etc.pp.).
I personally often build my own RPMs instead of using the straight
tarball. It's a bit more work, but it keeps the rpm database clean and
leaves me with all the uninstall and upgrade options a plain tarball
doesn't have.
And if the RPM I built was any good, I can also contribute them to Red Hat
contrib or other places... ;-)
Cheerio,
Thomas
--
"Look, Ma, no obsolete quotes and plain text only!"
Thomas Ribbrock | http://www.bigfoot.com/~kaytan | ICQ#: 15839919
"You have to live on the edge of reality - to make your dreams come true!"
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
