Hi! (mail style: brief, but friendly) If any of you have big plans for packaigng changes regarding kde4.3.0, now is the time to speak up with your plans and a timeline for accomplishing it and/or mentioning what help you need from others to accomplish it. Especially plans that requires NEW caused by packaging changes, and not caused by "new applications", or things that in general can cause breakages that we need to care about. My plans: Split kdebase-workspace-libs4+5 in seperate libraries. Done mostly by Martin Alfke with a bit additional cleanup by George Kiagiadakis and Modestas Vainius Kdebindings: pc files for the mono bindings, more mono packages. Split out krosspython and krossruby (antd other krossthings) to separate packages. /Sune -- Do you know how to overclock the 92-bit TCP/IP cache? You have to explore the terminale over a PCI BIOS, so that from ICQ you neither can telnet to the system on a proxy to a display, nor need to get access over the utility, so that therefore you should connect the kernel to boot a hardware of the POP3mail window over a sendmail on the mouse over the UltraDMA PCI computer.
On Jueves 02 Julio 2009 18:28:08 Sune Vuorela escribi?:> Hi! > > (mail style: brief, but friendly) > > If any of you have big plans for packaigng changes regarding kde4.3.0, now > is the time to speak up with your plans and a timeline for accomplishing it > and/or mentioning what help you need from others to accomplish it. > > Especially plans that requires NEW caused by packaging changes, and not > caused by "new applications", or things that in general can cause breakages > that we need to care about. > > My plans: > Split kdebase-workspace-libs4+5 in seperate libraries. Done mostly by > Martin Alfke with a bit additional cleanup by George Kiagiadakis and > Modestas Vainius > > Kdebindings: > pc files for the mono bindings, more mono packages. > Split out krosspython and krossruby (antd other krossthings) to separate > packages.Hi, Though I do not strongly oppose it, I think that making kross.* packages is overdoing it a little. It would be a one file package for a kdelibs library. I think it fits right in libkde4-ruby1.8, where you do expect to find KDE ruby libraries. I would like to consider other split for that package: ?libsoprano-ruby? to remove a dependency on the libkde4-ruby1.8 package
Hello, On 2009 m. July 3 d., Friday 02:28:08 Sune Vuorela wrote:> If any of you have big plans for packaigng changes regarding kde4.3.0, now > is the time to speak up with your plans and a timeline for accomplishing it > and/or mentioning what help you need from others to accomplish it. > > Especially plans that requires NEW caused by packaging changes, and not > caused by "new applications", or things that in general can cause breakages > that we need to care about. > > My plans: > Split kdebase-workspace-libs4+5 in seperate libraries. Done mostly by > Martin Alfke with a bit additional cleanup by George Kiagiadakis and > Modestas Vainius > > Kdebindings: > pc files for the mono bindings, more mono packages. > Split out krosspython and krossruby (antd other krossthings) to separate > packages.My plan is to migrate kdelibs5 (and workspace lib* probably) to symbol files when relevant support is in dpkg-dev. Since this will take time (on dpkg side), it will probably happen later in 4.3.x cycle. As a side effect, I plan to tie kdebase-runtime to API which typically only an application would use, but not a library (e.g. KAboutData). -- Modestas Vainius <modestas at vainius.eu> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: <http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20090703/bad31746/attachment.pgp>