#include <hallo.h> * Joe Smith [Wed, Oct 05 2005, 08:22:48PM]: > >I wonder why nobody did implement that feature before. I imagine > >(without knowing much about APT's internals), the pseudocode would look > >like that: > > > >- install command gets the list > >- if the package does not exist in the cache and the given string is a > > file, then: > > - read the metadata of this package > > - creating a virtual sources set containing that package and inject > > it somewhere in APTs graph representation. The access method > > would be "file:", and it should get the highest possible priority > > (at least higher than any seen priority) > > - install the prerequisites and then the package with the usual > > methods > > fi > > would it not be simpler to have have apt just ask dpkg what the > dependencies of the passed .deb are and then install the dependencies (and > their dependecies) and then just pass the deb directly to dpkg?
Hehe, it was my first thought about a possible solution, howerver: You also need the Conflicts string. And while the dependencies/conflicts are beeing installed, there may appear a constellation where the new package must be installed during the upgrade. And how would resolve that situation then? Eduard. -- Letzte Worte eines Fallschirmspringers bevor er in Bodennebel eintaucht: "Die Wolke nehme ich noch mit." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
