Hi

On Wed, Nov 5, 2008 at 2:31 PM, Piyush Soni <psoni6_at_mail.gatech.edu> wrote:
> Hi,
>
> I looked on the web FAQs etc., but didn't find anywhere the official process
> of "complete" removal of curl from the system. I'm using RHEL 4 and had some
> 7.12 version on it. Since it was giving problem with some other
> software(xml-rpc), I tried to install 7.19 on top of it(the latest version).
> But even that didn't work, so I thought of removing all versions and put
> 7.15.5 on it. But I don't know how to do it.
>
> I looked somewhere,
>
> rpm –q curl
>
> Then it will give the exact version /name of curl installed. So even if I
> had 7.19.0 installed on my system, it gave some 7.12 name, which I used in
> this command:
>
> rpm –e nodeps <the output of previous command>
>
> Now, it should have removed curl completely from the system, but it doesn't.
> When I type curl –version now, it gives me 7.19.0
>
> Again, if I type now rpm –q curl, it says that the package is not installed.
> I don't know now if it is installed or not, but when I search for curl files
> on the system, there are a LOT of it!
>
> Is there no clean way?

There is a clean way, but manually installing, removing or overwriting
software on a Red Hat system breaks the clean way.

Your question is really a Red Hat (or rpm) question, and not a curl question.

If you manually install non-RPM versions of software or if you
manually overwrite or delete software installed via RPM then "rpm -q"
will give you incorrect or unexpected results. If you manually
install curl 7.19.0 and run rpm -e curl, rpm will think that there is
no curl on the system, even though your manually installed one may
still be there.

i.e. don't do that.

It would be better to build an RPM version of curl and install that
using "rpm -i", but this is not guaranteed to work, because of other
packages that may depend on the older version of curl. You might be
able to get around that by using --nodeps, but then those things that
depend on the old version will likely break. It is best not to use
--nodeps or --force. If you insist on doing that, don't be surprised
when things break.

Regards,
Michael

-- 
Michael Wood <esiotrot_at_gmail.com>