On Sat, Mar 10, 2018 at 11:13:53PM +0100, Axel Beckert wrote: > Control: tag -1 + moreinfo > > Hi Bill, > > Bill Allombert wrote: > > There is a circular dependency between qutebrowser and > > qutebrowser-qtwebengine|qutebrowser-qtwebkit: > > Yes, I'm aware of that. > > Otherwise we would need two additional binary packages (with nearly > the same names as the existing ones) where one set would be meta > packages, pulling in the relevant dependencies and the other set would > be meta packages pulling in qutebrowser and the according dependency > package, e.g.
Do you really need two additional binary packages ? For example: Rename qutebrowser -> qutebrowser-common qutebrowser-qtwebengine -> qutebrowser + Provides qutebrowser-qtwebengine Change qutebrowser and qutebrowser-qtwebkit to Depend on qutebrowser-common. Change qutebrowser-common to not depend on qutebrowser-qtwebengine|qutebrowser-qtwebkit > (*) Will be difficult to cause problems with buster to stretch updates > since qutebrowser is not in stretch, so there can't be any upgrade > issues from stretch to buster. Of course not, it cause problem during buster to buster+1, at a point where fixing buster is not an option anymore. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
