On Monday 16 November 2009 04:16:10 pm Chani wrote: > On November 16, 2009 13:52:58 Ingmar Vanhassel wrote: > > Excerpts from Chani's message of Mon Nov 16 22:26:16 +0100 2009: > > > interesting... > > > given that packagers have to split up kde applications anyways, could > > > it be *good* to offer individual tarballs? if so, wouldn't now be the > > > least painful time to make such a change? what if kdegames was a > > > gitorious project with 39 repos (assuming one extra for shared stuff)? > > > > Speaking as a packager, it would be simply great to provide individual > > tarballs for some modules. > > > > I care less about splitting kdelibs, kdepimlibs, and the > > kdebase-runtime, kdebase-workspace modules. Modules like kdenetwork & > > kdegames, which as someone put it earlier, are more like an aggregation > > of projects, are a different matter though. Those modules have a > > relatively simple dependency tree in the module, and it shouldn't be too > > much effort to split those up. > > > > And yes, I'm prepared to help in this effort and I'm confident that I'm > > not the only packager who is. > > well... if we have people volunteering... why not, eh? :) > my main concern about it was that it'd be work that someone has to do. > > btw... it'd probably be a good idea to talk to some of the biggest > committers to such modules. after all, they're going to be among the main > users, it seems like this discussion should involve them... >
Personally, I'd love to split kopete from kdenetwork (and still keep all the benefits of being part of a main KDE release) since I'm really only interested in working on Kopete. I couldn't care less about the rest of kdenetwork (even though there are some great apps in there) since I generally don't touch the code. -- Matt _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
