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. -- Exherbo KDE, X.org maintainer _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest
