Request for review: koffice

[Andreas Bierfert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?

- - Andreas
- --
Andreas Bierfert               | http://awbsworld.de      | GPG: C58CF1CB
andreas.bierfert at lowlatency.de | http://lowlatency.de     | signed/encrypted
phone: +49 2402 102373         | cell: +49 172 9789968    | mail preferred
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFC4JTuQEQyPsWM8csRAj+aAJ9TiWAZFWqG9j0LzIEsNYiwkUkqLQCdHByl
J2U+9Yl7ap33Wn2JJsexiMo=
=nIwA
-----END PGP SIGNATURE-----