Chuck Dale <[EMAIL PROTECTED]> writes:
> Ah poor man.. RPM rocks and you are missing out on a lot of coolness.
>
Ah, yeah, so I am a very poor man too ...
No, rpm doesn't rock that much. A really rocking thing should be able to detect
that you DO HAVE the needed stuff even you didn't use rpm to install it !!!
Isn't "configure" able to do so ?? Does it require some specific installation
tools ??? Why not rpm ?? Will ultimately rpm be the Winbucks counterpart of the
"setup.exe" mechanism by simply removing the --force or --nodeps that I am sure
I am not the only one to need quite often ???
What do you do when you have software like gnome which CAN use some libs but don't
NEED them ?
Philippe
> The only times it doesn't work so well is when
> the user doesn't understand exactly how it works or why it does
> something a certain way. Reading Maximum RPM showed me the depth of RPM
> and why it is definitely not just an eye candy thing like a Windows
> installer and is actually a system level solution to difficult problems
> in the Unix structure.
>
> In countless RedHat installs I've never had any problems with RPM other
> than my own mistakes or misunderstandings. And it's been working fine on
> my home install for more than a year. No database problems at all..
>
> And --force is definitely the stone age man's club in the RPM toolkit, I
> would recommend playing along rather than trying to fight like a real
> hard core Unix man.
>
> Regards,
>
> Chuck
>
> Wrote lloy0076 on Wed, Mar 01, 2000 at 12:58:02PM +1030:
> >
> > HEHEHE
> >
> > I avoid use RPM as much as I can. If I ever use it I always use --force.
> > The RPM database seems to fall over even worse then the Windows Registry
> > if I may say so myself. It's good for a system where ALL YOU EVER
> > install is RPM'ed, and it's on high reliability but other than that it's
> > caused me far too much grief to be bothered.
> >
> > I don't try to pretend that Linux is Windows and just use make and
> > ./configure.
> >
> > DAVID
> >
> >
> > --
> > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> > as the Subject.
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
