> > ../configure
> > mmake
> > make install
> >
> > It's the only thing I've found "easy" with Linux so far!
> >
> > I don't know how it's done with a RPMed package but I don't
> see how it
> > can get any easier?
>
> O thqts easyier, suppose your cdrom is mounted or you have downloaded
> a rpm file, go to the dir where the file is, do; rpm -i <filename>
The mail problem us uninstalling. I hate having stuff in my registry/system
directory that isn't used anymore in win. I dont want the same thing to
happen in linux with stuff in my bin directory. "WTF is that? I dunno,
something must have *installed* it and I don't know what it is".
install:
rpm -i somepackage.ver1.rpm
update:
rpm -U somepackage.ver2.rpm
uninstall:
rpm -e somepackage
the nice thing about rpm is that it creates a databse of what you have, and
this databse includes a description
what package does \usr\bin\IDunno.gif belong to?
rpm -f \usr\bin\IDunno.gif
what other files has this package installed?
rpm -l (or -ql) thatpackage
and what the hell is it?
rpm -qi thatpackage
I would _hope_ that a make install will not copy stuff to my /bin directory,
but only create symlinks so that the software can be easily uninstalled, but
fact is I dont know _what_ make install is going to do. With rpm, I can
browse the packages I have with GnoRPM or Krpm, and I have a clean
uninstall.
