Micah, I understand that there isn’t always a compatible Lightning available. But like I said, I’m having trouble imagining a user that wants to upgrade Thunderbird anyway, only to discover _after_ the upgrade that there’s no compatible Lightning.
I also understand that, _if_ a user who wanted Lightning had gotten into a bad situation where there’s no Lightning compatible with their Thunderbird version, then they might want a working version installed automatically when it becomes available. But they’ll be happier if we avoid putting them in that bad situation to begin with. My questions above remain unanswered (what makes _this_ versioned dependency special, and why do users want (c) instead of (a) or (b)?). (By the way, I assumed the appropriate maintainers would be automatically informed when I submitted the merge proposal; please let me know if I should have done something different.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839130 Title: Add versioned package dependency for maximum XUL application version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightning-extension/+bug/839130/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
