| Summary: | Split KOffice into individual packages | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | other (any) | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | albator78, bugwatch, darrella, michele.calgaro |
| Priority: | P1 | ||
| Version: | 3.5.13.x [Trinity] | ||
| Hardware: | All | ||
| OS: | All | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Darrell
2011-03-29 14:35:54 CDT
Based on discussion in the developer's list, the reasons stated likely do not apply. The consensus is to keep KOffice as a "light-weight" office suite. With that support, splitting the packages remains a good idea. The suite requires more than an hour to build and troubleshooting compiling bugs is frustrating when the build fails at about 90%. If the apps were split into individual packages then troubleshooting could be focused on the failure without needing to rebuild the entire suite. Apparently some distro maintainers have split the packages successfully so this should be doable. I'm almost tempted to change this to a bug. Please consider this enhancement for R14. Koffice is a bear to build and only few packagers try. Even on a dual core system koffice requires more than an hour and a half to build. Having the build fail at an hour and twenty minutes is disheartening. Building as components would alleviate many build problems. Does this bug still apply ? Which distribution are you referring to ? AFAIK the Koffice package is already split in several packages on most distributions. At least it is in the RPM packages, and if I remember well, I wrote them by copying the Debian/Ubuntu packaging files, so it was split there too ... Slackware. Possibly this can be resolved through build scripts and packaging. I haven't tried to explore that possibility. Koffice will remain as a suite, since it is a suite. |