Request for review: koffice

[Jeff Pitman]

On Friday 22 July 2005 14:40, Andreas Bierfert wrote:
> Jeff Pitman wrote:
> > That's what I was thinking. This is what I'm doing for
> > Python-Twisted 2.x, who've split their packages and use different
> > Versions for each sub-package. Doing so creates an upgrade path
> > from the previous monolithic package.
>
> Just one question with this: Having a koffice-suite package which
> obsoletes koffice (and -i18n) and Requires all the subpackages from
> the new version should do the trick on update. The question is what
> is needed in koffice-core? Also Obsolete the old version or Conflict
> the old version? What is the best way to go?

Conflicts makes the most sense, to me.  I don't know what others think.  
Usually you only want one package Obsoleting another.  Most of this 
happens due to renaming of the package.

-- 
-jeff