Stefan Monnier <monn...@iro.umontreal.ca> writes: > With emacs20 (and even more so emacs19) still installed, it's very common > for an elisp package to work well with some Emacs flavors but not all. > Byte-compilation is not necessary for packages to work, usually, so > failure to byte-compile a package should simply not be considered as > a failure to install the package.
At the moment, both with respect to this and the original issue, I'm inclined to think that it really shouldn't be any of emacsen-common's business. i.e. if an add-on package doesn't work with a given older emacs, then that package should add appropriate guards, and if an add-on package knows that it's safe to continue even after some part of its install/remove scripts fail, then it should just make sure that those scripts exit without an error status when appropriate. Though I'll think about it a bit more -- perhaps I can convince myself otherwise. Thanks -- 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
