Sven Joachim <svenj...@gmx.de> writes:
> Probably we're talking at cross-purposes here, but surely the new flavor
> should provide emacs25 just as the existing emacs25-nox and
> emacs25-lucid flavors already do?
As far as I understand it, nothing can provide emacs25 except for the
emacs25 binary package (because emacs25 already exists as a binary
package)[1].
Hence the need for "something else" for the "provides", and so far it
sounds like {emacs,xemacs}XY-any might be least worst.
But even with that, as suggeste, I think we'll be stuck with 2 deps
per-flavor because virtual-only deps are disagreeable, e.g.:
emacs25-nox | emacs25-any | emacs24-nox | emacs24-any
[1] Which is also why (iirc) for a long time there was no emacs
meta-package (because before emacs19 (I think), the Emacs package
was just "emacs").
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
