On Thu, 2003-07-17 at 20:47, Thomas Backlund wrote: > Viestiss� Torstai 17. Hein�kuuta 2003 22:21, Andi Payn kirjoitti: > > On Thursday 17 July 2003 11:59, Olof Bjarnason wrote: > > > Thanks for your advice, although I have some more questions :) > > > > > > #> Is this a bug? > > > #No. > > > > > > If not a bug - what is it? Should the combination of actions > > > which I took not lead to installation of a "custom" rpm? > > > This implies there are 'special' packages, or Mandrake-packages, in > > > which case at least I would favor a notification upon clicking on > > > such a "foreign" package. For example, it would be helpful if > > > Mandrake tells me "Warning: Non-Mandrake package. Install > > > manually with urpmi" when I click on my 'abc.rpm'. > > > > The urpmi tools are not about packages, but about urpm sources, which are > > repositories of packages. > > > > So, the short answer is: You must build a custom urpm source containing > > your custom packages before you can use urpmi to install those packages. > > Just copying the rpm's into a directory is not enough. > > > > Not entirely correct... > > If you copy a rpm (or many rpms...) to an empty directory, > and issue ' urpmi * ' in that directory, urpmi will try to install all > packages in that directory, trying to resolve the dependencies by using the > packages in that directory and the packages known to it through it's defined > sources... > > Of course if urpmi still can't resolve the dependencies for some of the > packages, it won't install those...
Andi meant to write "You must build a custom urpm source containing your custom packages before you can use rpmdrake to install those packages." -- adamw
