--nextPart1474988.SKTyQdsAQ5 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 14 November 2006 02:01, Thiago Macieira wrote: > Kevin Krammer wrote: > >On Monday 13 November 2006 23:14, Aaron J. Seigo wrote: > >> i can see the following options: > >> > >> - the two teams agree to work on one codebase > >> - do the same thing we did with cd burners and put them all into KEG > >> and let user demand sort it out > > > >Right, the Salomonic solution. Nobody wins, everybody looses. > > Unfortunately the only fair option beside the optimal first one :( > > I wouldn't say that everybody lost in the CD burner debate. We had three > applications at the time, not counting KOnCD. And a clear winner > survived. I don't remember exactly, but I am not sure the CD burner conflict meant=20 removing something from a "main" package and moving it to KEG. With "everybody looses" I meant that no projects is allowed into a main=20 package and the main package looses the PDF viewer. Anyway, there are only three "fair" solutions: 1) both are in kdegraphics 2) neither is in kdegraphics 3) a single program (either a merged on or if one becomes unmaintained) is = in=20 kdegraphics It seems (3) is not very likely. (1) won't be a problem for most of the people, but will trigger the "oh boy= ,=20 KDE has three text editors" trolls. The actual problem is packaging. There is no problem in having two similar= =20 programs in the same sub repository, no problem in having them released at= =20 the same time, but since some distributions create just one single package= =20 per SVN module, there will be a redundancy at installation time. Since this packaging policies are not going to change soon (unfortunately),= =20 I'd even say that any feature rich application should not be in a module th= at=20 gets handled this way (unless they are a combined thing like KOffice) Cheers, Kevin =2D-=20 Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring --nextPart1474988.SKTyQdsAQ5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFWbSvnKMhG6pzZJIRAlPtAJ4rWWIy4Yphypf3e8zSMzotDDn0wQCfR6sz btYAahpxtIGvb49OszYMaJM= =to8c -----END PGP SIGNATURE----- --nextPart1474988.SKTyQdsAQ5--