On 07/21/2011 09:03 AM, Milian Wolff wrote: > Milian Wolff, 21.07.2011: >> Rex Dieter, 21.07.2011: >>> Hi, been working on the adapting packaging for our new split tarball >>> world order, and have run into a bit of a quandry wrt kdelibs and kate. >>> >>> Prior to the split, libktexteditor and katepart were nicely bundled >>> together in kdelibs. So, anything linking libktexteditor naturally had >>> an implementation available, and it "just worked". This is no longer >>> true. >> >> This is not true. KDELibs never shipped an implementation of the >> interfaces. You always needed kate installed from kdesdk for those apps to >> work. > > Or thinking about it: I'm actually not sure, was katepart in SVN days in > kdelibs? Anyhow, if so the "solution" would be to split kate tarball and > create a katepart package that other packages can depend on.
Yes it was. That's my point. I guess I'm implicitly arguing that splitting libktexteditor and katepart into separate pieces is arguably a *bad idea*, at least packaging-wise. still wondering how other (particularly rpm-based) packagers are handling this case... -- rex _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
