Hi all,

I agree with Cyrille, for now the marble flake should move to playground.
There it can depend on both, edu and koffice with no problem and simply have 
normal version checks.
This will allow to work on the flake as needed and avoid svn-externals 
(remember, they are evil).

Since koffice 2 is not released yet, we really cannot depend on it, and I don't 
see the point in shipping the flake with kde-edu if no koffice is installed.
IMHO this also prohibits extragear for now at least until there has been a 
release of koffice and marble provides some stable api.

In the future, I wonder if not koffice might be the appropriate place for the 
flake (with optional edu dependency).
If it is not acceptable to demand edu to be built before office or the flake libs 
are moved to kdelibs, it needs to be in extragear.
Being in extragear should be good, especially if Cyrille's offer to release 
along with koffice is accepted :)

Greetings,
Frederik


On Wednesday 04 June 2008 10:29:45 Anne-Marie Mahfouf wrote:
> On Wednesday 04 June 2008 10:16:20 am Anne-Marie Mahfouf wrote:
> > On Tuesday 03 June 2008 10:48:01 pm Thomas Zander wrote:
> > > Maybe with the new data point that Annma brought up (unwanted module
> > > dependency) we should re-evaluate this option?
> >
> > What I ask is:
> > - make kdeedu compile without asking for KOffice to be updated
> > - add a note to packagers so they know exactly what to package and how
> > - have cmake clear outputs for users who build from sources and for
> > packagers as well
> >
> > And it would be nice not to discuss that sort of things in public mailing
> > lists, here KOffice-devel and kde-edu and to first ask the KOffice
> > packager point of view and the kdeedu coordinator point of view. Those 2
> > are part of KDE release team and can enquire further to other people if
> > necessary.
>
> Sorry I meant:
> And it would be nice to discuss that sort of things in public mailing
> lists, here KOffice-devel and kde-edu and to first ask the KOffice packager
> point of view and the kdeedu coordinator point of view. Those 2 are part of
> KDE release team and can enquire further to other people if necessary.
> (not to discuss it in private)
>
> _______________________________________________
> kde-edu mailing list
> kde-edu@mail.kde.org
> https://mail.kde.org/mailman/listinfo/kde-edu

_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu