Hi Bill, On 06-09-15 16:42, Bill Allombert wrote: > There is a circular dependency between winff, winff-gtk2 and winff-qt:
That was on purpose, but see below. > > winff :Depends: winff-gtk2| winff-qt > winff-gtk2 :Depends: winff > winff-qt :Depends: winff > > Circular dependencies are known to cause problems during upgrade, so we > should try to avoid them. > See threads > http://lists.debian.org/debian-devel/2005/06/msg02111.html > http://lists.debian.org/debian-devel/2005/11/msg01101.html It seems I had forgotten that is was so bad. I'll have to add an additional package than because I don't see a nice way out otherwise: I build to "programs" winff-qt and winff-gtk that both require data in the winff package (see the bug 772682). However, the user would typically install winff and doesn't really care which winff-qt or winff-gtk gets installed, but expects one or the other. I think I'll have to create a winff-common package and make winff an empty package that is only there to "Depends" on winff-qt or winff-gtk. Do you have a better idea? Maybe an alternative would be to put the data in both packages and let them "Replaces" each other, such that the data is only there once, but dpkg doesn't complain. The point being, I don't like to add a new package for this (as any package is a "burden"), but I also think it is unnecessary for these packages to conflict (they are happily running alongside each other on my system). Paul
signature.asc
Description: OpenPGP digital signature
