Toby Speight <[EMAIL PROTECTED]> writes: > What happens if emacsen is installed *after* package 'foo' that uses > it? AIUI, foo won't get its emacs components configured at all then.
Actually now that I've thought about this yet further, I don't think this is a problem. If emacsen-common is being installed after foo, and if that's because one of the various emacs flavors is being installed, then that flavor will handle the emacsen configure for foo, and if emacsen-common is just being installed by itself (no flavor of emacs), then that's not a problem either, since you couldn't actually use foo anyway. -- Rob Browning rlb @defaultvalue.org, @linuxdevel.com, and @debian.org Previously @cs.utexas.edu GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
