On Wednesday 19 April 2006 12:22, Thiago Macieira wrote: > Matt Rogers wrote: > >> I don't like being in kdeextragear because: > >> a - Users don't beleive it is a part of the core kde application. > > That's a misconception. And given the possibility of restructuring for > KDE4, extragear may gain more importance. > > We'll have to see. > > >> b - We don't get translation > > This is false. Extragear applications are translated too. > > >> c - We have to take care about our own schedule. > >> > >> But kdeextragear is nice because > >> d - We can release more often. > > (c) and (d) are contradictory. You cannot dislike something and find it > nice at the same time. > > >> e - User can upgrade only Kopete without upgrade the whole KDE (at > >> least kdelibs+kdenetwork) > > You don't have to be in extragear to do that. In fact, Kopete *should* > create tags out of KDE/kdenetwork too. > > >> Also I don't think it is justified to have kopete as a "module" > > Nor do I. We're looking into making modules more modular, so there's no > reason to create an entire new module for a single app, however big it > is. > > >there are more than 235,000 lines of code in kopete. We have our own > > library, application, and plugins. IMO, that's plenty of justification. > > Yes, kopete is probably larger than kdetoys, kdeutils and kdesdk combined, > but it's still one single application.
and so is kdevelop. what's the difference? _______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
