| Summary: | KDE4Workspace__ hacks should be explained and documented | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chris Bruner <cbruner> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | robin.atwood, sh |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Chris Bruner
2009-06-05 20:12:57 UTC
Use kdevelop-9999 ebuild from kde-testing overlay.
You're reporting bug - compilation problem - but *not* using ebuild - this bug is invalid to me, please report bugs only in *Gentoo packages*.
KDE4Workspace__ thing is something we need to explicitly override because it breaks our split-ebuilds rule.
Should be closed as WONTFIX.
src_prepare() {
# Remove this and the ksysguard dep after libprocessui moved into kdelibs
sed -i -e 's/${KDE4WORKSPACE_PROCESSUI_LIBS}/processui/g' \
debuggers/gdb/CMakeLists.txt \
|| die "Failed to patch CMake files"
}
If you're interested how to make it compile outside of Gentoo.
Thanks for the help, but now it gives me undefined reference. I don't think the fix was correct. I would be happier building it within gentoo but I don't have an ebuild for it, and if I can't build it buy hand, I don't know how it would work better remotely. And I've never had luck building my own ebuilds. I have just tried to compile kdevelop using the latest kdevelop-9999 ebuild form the kde-testing overlay and although I no longer the error about KDE4Workspace__processui, the compile fails later because the KsysGuard libraries are not being linked to: [ 48%] Building CXX object tools/grepview/CMakeFiles/kdevgrepview.dir/grepoutputmodel.o CMakeFiles/kdevgdb.dir/processselection.o: In function `GDBDebugger::ProcessSelectionDialog::pidSelected()': processselection.cpp:(.text+0xce): undefined reference to `KSysGuardProcessList::selectedProcesses() const' CMakeFiles/kdevgdb.dir/processselection.o: In function `GDBDebugger::ProcessSelectionDialog::ProcessSelectionDialog(QWidget*)': processselection.cpp:(.text+0x1c9): undefined reference to `KSysGuardProcessList::KSysGuardProcessList(QWidget*, QString const&)' Any idea how to fix this? TIA (In reply to comment #1) > Use kdevelop-9999 ebuild from kde-testing overlay. > > You're reporting bug - compilation problem - but *not* using ebuild - this bug > is invalid to me, please report bugs only in *Gentoo packages*. > > KDE4Workspace__ thing is something we need to explicitly override because it > breaks our split-ebuilds rule. > > Should be closed as WONTFIX. Why exactly? It should still be possible to use a Gentoo machine to build custom software against the installed libs. For example if someone wishes to contribute to kdevelop it is useful to be able to build it manually outside of an ebuild. (In reply to comment #4) > (In reply to comment #1) > > Use kdevelop-9999 ebuild from kde-testing overlay. > > > > You're reporting bug - compilation problem - but *not* using ebuild - this bug > > is invalid to me, please report bugs only in *Gentoo packages*. > > > > KDE4Workspace__ thing is something we need to explicitly override because it > > breaks our split-ebuilds rule. > > > > Should be closed as WONTFIX. > Why exactly? It should still be possible to use a Gentoo machine to build > custom software against the installed libs. > > For example if someone wishes to contribute to kdevelop it is useful to be able > to build it manually outside of an ebuild. It might be useful to provide feedback to upstream about kdevelop, but it certainly is not a Gentoo bug. The Gentoo KDE team provides ebuilds to build KDE packages for Gentoo - including ebuilds for tracking upstream live tree. When someone chooses to ignore them and to build software manually, then one gets the responsibility of picking up the pieces when stuff breaks. If I may suggest a warning during the build of kdebase-workspace libs (I think they're called libkworspace now) telling to do a sed on the CMakeLists.txt file if you try to compile stuff by hand and have this issue would save a lot of people some lost time, I also ran into this with kdevelop but probably there are other packages suffering from the same problem. Certainly Gentoo's bugzilla is not the place to report issues of your own development/packaging attempts with <your-favourite-IDE> as we can't be responsible what you put in your own CMakeLists.txt (or similar) The reason I posted this in the first place is that the problem occurred due to the way gentoo was building kde. Upstream wouldn't look at it saying that because gentoo was building kde with a strange library layout (slots I guess) they weren't interested in fixing it. So if upstream won't fix due to gentoo bug, and gentoo won't fix due to upstream where should I be going? (I no longer have this problem BTW) |
