On Tue, 22 Feb 2000, Carl A. Cook wrote:
> Well, I think he's concerned about MISSING dependancies, which you certainly
> will with --nodeps.
>
> The mdk packages are different from others. Actually installing a non-mdk
> package should raise MORE alarms than an mdk package, rather than less, because
> it might not recognize when a packge IS actually installed.
>
> Comments, MandrakeSoft?
Yeah can you say that again in english please. What the h**l are you guys
talking about the _only_ way your going to have problems is if you were to
install say foo-0.1-1mdk and you wanted to to install another package
foo-0.1-1, it'll complain that it is older than what you have, in which
case you would use --oldpackage. Now if someone puts in foo.spec
Requires: bar-%{version}-%{release}
They either A) don't understand specfiles and made a mistake, or
B) really mean it needs that specific dependancy for whatever reason.
> --
> Carl A. Cook
> quantumATaugustmailDOTcom
>
> Sign the petition at http://www.libranet.com/petition.html
> Help bring us more Linux Drivers
>
>
> Rene Scott wrote:
>
> > Hi,
> >
> > try rpm --nodeps ..., and check out rpm(8).
> >
> > Rene
> >
> > On Feb 21 seanc wrote:
> >
> > > Many packages assume normal naming and not the mdk added so dependancies
> > > for rpms aren't realized even though they exist.
> > >
> > > eg. gnome-pilot,gnome-pim (as they were looking for gnome-pim dependancies
> > > though the installed versions where gnome-pim-mdk ....)
> > >
> > > Any easy ways around this?
> > >
> > > Sean Cody ([EMAIL PROTECTED])
> > > "Codito ergo sum" (I code therefore I am)
> > > Rasterman
> > >
> > >
> >
>
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
