Should we remove every versioned dependency from the Ubuntu archive, then, just because people running beta versions accept some risk that there will be periods where some packages might not work? Say precise is in the middle of a Perl transition—should all the packages depending on old Perl just remain on my system in a completely nonfunctional state while Perl is upgraded anyway, just because the maintainer thinks that I chose to accept that I can work without those packages for a few days, but it’s too inconvenient to temporarily uninstall them?
If not, what makes _this_ versioned dependency so special? It seems to me that a user either (a) wants Lightning, in which case they’ll have the package installed, and they’ll want incompatible upgrades blocked, or (b) doesn’t want Lightning, in which case they’ll just uninstall the package, on the off chance that it was installed to begin with. I have trouble imagining your hypothetical user that (c) wants Lightning but is happy to have it taken away from them for a few days by surprise on any system upgrade. If you want the (a) users to be willing testers of Thunderbird betas and Ubuntu betas, the answer is to upload compatible versions of Lightning, not to try to force them towards (c). -- 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
