[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Outrageous Maintainer

On 4 May 2005, at 6:39 pm, Wouter Verhelst wrote:

On Wed, May 04, 2005 at 04:35:25PM +0100, Tim Cutts wrote:
On 1 May 2005, at 8:53 am, Wouter Verhelst wrote:
True. However, it does no harm to add the conflicts, while it does make it easier for your users. When presented with a bug in another package that completely breaks mine (rather than the entire system), usually I
do add the conflicts: header.

I think that's a dangerous thing to do.  When the bug in the other
package is fixed, the chances are that you won't know about it, and
then you'll end up with two packages which conflict with each other for
no reason.

That's why we have versioned conflicts. Also, when adding a conflicts to
another package that is buggy, it would be _extremely_ bad form to not
track that other package for when the bug is fixed -- or, at least, to
file or reassign a bug to that package.

Good point - I'd forgotten about versioned conflicts (never having needed to use one!).

It causes no harm, as long as one is careful. And isn't being careful
something you should be doing anyway?



Dr Tim Cutts
GPG: 1024/D FC81E159 5BA6 8CD4 2C57 9824 6638  C066 16E2 F4F5 FC81 E159

Reply to: