+1 for the kdeplasmoid module. In this module, we can release dataengines too and other stuff around plasma (containments and so).
It allows to ship with kdebase basic plasmoid for desktop use and in kdeplasmoid we can put plasmoids that correctly works with plasma but not needed for basic desktop interaction (ie frame, binary clock...). For me this : http://websvn.kde.org/trunk/KDE/kdebase/workspace/plasma/dataengines/nowplaying/ don't need to be in kdebase (it depends of amarok wich is in extragear) but in the new module kdeplasmoid. isn't it? Br. 2008/5/20 Allen Winter <[EMAIL PROTECTED]>: > On Tuesday 20 May 2008 06:07:12 Dirk Mueller wrote: > > > On Sunday 18 May 2008, Tom Albers wrote: > > > > We discussed this earlier. Can we move extragear/plasma to a new kde > main > > > > module kdeplasmoids (or some other name) ? > > > > > > isn't there at least one plasmoid in there that is supposed to work? > nobody > > > says that we have to include all of extragear-plasma :) > > > > > > I still think its a good idea to have a kdeplasmoids module that is > > > released together with KDE, as it avoids the constant api breakages we > had > > > with extragear-plasma being in sync with /trunk and not compiling with > any > > > branch. > > > > > > I was contacted lately on how to do extragear-plasma releases together > with > > > KDE, I think this is the way to go. > > > > > > > Does anyone actually object? Shall we pick a date to do the move? > > > > > > Identify which plasmoids we can pick up and do it (IMHO). > > > > > I think a kdeplasmoids module is a very good idea. > > However, before we create one I think we should have a module coordinator > in place. > > And is it too late given that today is beta1 tagging? > > -Allen > > _______________________________________________ > Panel-devel mailing list > [EMAIL PROTECTED] > https://mail.kde.org/mailman/listinfo/panel-devel > >
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
