Compiling on you're own system by and large has an advantage
of optimising for your own processor rather than a a vanilla i386
486 or what ever machine the rpm was compiled for.
On the down side,over a period of time, you may find that you'll
need to update some system link files (*.jpeg 6a or 6b comes to mind)
When you do, you could break some of the older programs.
Just a thought.
--
_________________________________________________________________________
Linux, the choice | "They're unfriendly, which is fortunate,
of a GNU generation -o) | really. They'd be difficult to like." --
/\ | Avon
_\_v |
|
-------------------------------------------------------------------------
--- Begin Message ---
Maybe this is a different thread, but why are you using rpm ? Why not get
the source and do it all by hand ? I've always mistrusted rpm and appget et.
al. as it seems to me like turning over too much control to entities whose
first interest is not me. My goal is to have machines with zero software I
havn't built from source. Am I the only one ?
On Thursday 11 October 2001 21:14, Ken Ambrose wrote:
> Okay -- something must've gone FUBAR while using RPM to "rpm
> -e" something. If I do to "rpm -i" foo, it tells me that bar is
> installed. If I go to "rpm -e bar", I'm informed that bar is *not*
> installed. I did an "rpm --rebuilddb" to no effect.
>
> How do I get rid of the incorrect dependency?
>
> Thanks,
>
> -Ken
>
>
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
--- End Message ---
