Rob Browning <r...@defaultvalue.org> writes: > However, to demonstrate why I'm beginning to think the current approach > may be unworkable, consider the case where no emacsen-related packages > are installed and someone runs this: > > apt-get install emacs24 add-on-depending-on-add-on-1 add-on-1 > > What should happen if the postinsts fire in the order listed? When > add-on-depending-on-add-on-1's postinst fires, add-on-1 isn't > "installed", and so add-on-depending-on-add-on-1 should be skipped > (though that may actually be broken right now), and then when add-on-1's > postinst fires, it's not (currently) going to do anything about the > other add-on because add-on-depending-on-add-on-1 isn't a dependency for > add-on-1.
Oh, and of course, one way you might try to fix this is arrange to have every add-on "install" every add-on that depends on it (and is ready). So then every add-on would be trying to install both its upstream and downstream dependencies. But even if we could do that sanely, we'd end up running even more redundant installs. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lisp-devel
