Re: replacing conflicting packages

[Richard Braakman <dark@xs4all.nl>]

Christian Hammers wrote:
> Hello List
> 
> I have two sets of packages: A1,A2.. and B1,B2,B3... which each provides a 
> working system (in this case a database) and conflict to each other.
> 
> My intend was now to show the user - when he tries to update just one
> component - that that is not possible and he should update all or nothing.
> Therefore I make every A* packet depend on A1 and every B* packet on B1 and
> let them conflict. (I would have this situation anyways).
> 
> The Problem is now that when installing say B2 it first tries to overwrite
> an A* packet and *then* complains about the conflicting dependencies.

If B2 and A2 overlap, then they must also conflict.  Conflicts that
are inherited via dependencies will indeed not work to prevent
overwrite errors, because depends are only checked at the
configuration stage.

> Of course B2 can not be allowed to overwrite any of the A* packets but
> I get many bugreports now that claims this behaviour as bugs :-(

Just add a lot of conflicts :-)

Richard Braakman