On Thursday, 2009-05-07, Tom Albers wrote: > Hi DIrk, * > > As discussed today, we would like to have a kdepim-runtime tarball, we > would like to have it contain the content of /trunk/KDE/kdepim/akonadi. It > should be able to compile stand alone and only contains the stuff that is a > runtime dependency for akonadi application. > > That way for example Mailody can depend on that package instead of > depending on the whole of kdepim. > > We should decide about the renaming kdepim/akonadi to > kdepim/runtime/akonadi or we could create a kdepim-runtime next to kdepim > as top level folder. I really don't care about what solution will be taken > as I can not oversee the build consequences at all. So I think the experts > should give their opinion about that.
Some parts in kdepim depend on private/module libraries in there, e.g. the Akonadi KResource plugins depend on some classes of the type specific helper libraries (kcal/kabc). Might also be true for kpilot/kjots/kcontactmanager Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
