"Davide G. M. Salvetti" <[EMAIL PROTECTED]> writes: > Just one comment, possibly meaningless: setting debian-emacs-flavor in > emacsen-common would make it easier to control which Debian flavors do > exist and what they actually are.
Maybe, but I'd rather not have to modify emacsen-common *just* because a new flavor comes out. > Leaving it to the emacs binary packages would require every single > package to be updated if something had to be changed, and we know this > could take time. I'm not sure I follow. The *only* thing we're talking about here is the setting of *one* symbol (setq debian-emacs-flavor 'foo) And the simplest place to do that is in the actual emacs binary since when it's done there, it requires *no* tests, conditionals, or other means to determine what flavor it is. The binary *is* the flavor. If I put something like this in emacsen-common, I'd have to have all kinds of checks to figure out which flavor is actually running the .el file. Not fun. > An example: I don't know what the many different Japanese xemacs > versions are for, but one day we could find it useful to let add-on > packages know which one is being run. Who knows? Right, but this would just require them to define unique symbols, and modify themselves to provide the correct directories. The latter's not something I could easily do from emacsen-common anyway. -- Rob Browning <[EMAIL PROTECTED]> PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
