Checkinstall questions

[Tim Wunder]

Previously, edj chose to write:
> Got checkinstall, tried it with gcombust and, after a few stumbles on my
> part, worked like a charm.  I have 2 questions, though.
<snip> 
< ...In short, how does checkinstall "conform" the
> program to my system?
>

Too add on to what Doug said, and to point out the obvious, checkinstall will 
only install a program that's been compiled by you. It essentially replaces 
the "make install" portion of installing from source. If you've managed to 
compile it, you certainly have the libs, dependancies, et al required to 
install the software. Checkinstall just packages it up for you and installs 
it in such a way that your rpm database knows about it. It's a great tool, 
but it's hardly magical.

So, that being said, what's the significance of the architecture string? 
AFAICT, nothing. At that point, the program is already compiled and changing 
what checkinstall will call it will not change the architecture it was 
compiled for. You need to do that with the ./confgiure script, during the 
compile process.

Regards, 
Tim

-- 
Caldera eWorkstation 3.1, kernel 2.4.9, KDE 2.2.2 from source, Xfree86 4.1.0
 12:00pm  up 4 days, 12:35,  2 users,  load average: 0.00, 0.00, 0.00
It's what you learn AFTER you know it all that counts