Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 330815

Summary: kde-base/kcachegrind: Allow installation of qcachegrind
Product: Gentoo Linux Reporter: Ari Entlich <atrigent>
Component: [OLD] DevelopmentAssignee: Gentoo KDE team <kde>
Status: RESOLVED WONTFIX    
Severity: enhancement    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Ari Entlich 2010-08-02 10:28:50 UTC
QCachegrind is a program which is like KCachegrind and is included in the kcachegrind source code directory, but doesn't depend on any KDE stuff. It's not installed by default. Also, I'm not entirely sure how complete it is, but it does seem to have a similar size (in terms of lines of code, at least) to kcachegrind.

Reproducible: Always
Comment 1 Maciej Mrozowski gentoo-dev 2010-09-18 17:47:02 UTC
Question - why? :)
I don't really see the point in installing something upstream clearly doesn't want to.
Sorry, that's a no go.
Comment 2 Ari Entlich 2010-09-18 20:21:07 UTC
Because I don't want to have to deal with KDE's dependency bloat. Other bugs which would mitigate the issue (such as bug 330817) are not being fixed, so this is a good way to sidestep the issue.

Although there is a README in the qcachegrind directory saying that it is mostly example code, a cursory look at the SVN log and source code suggests to me that it is pretty complete. In addition, it gets first-class treatment in the main README file for the whole package, and simple compilation instructions are given.

If you want to discourage people installing it, you can mask the USE flag. If you don't want to deal with this right now, feel free. But don't close it just to make your bug list shorter.
Comment 3 Maciej Mrozowski gentoo-dev 2010-09-21 22:28:21 UTC
At this time being this feature request *is* invalid.
When it's officially available in buildsystem (not just in outdated README files), we will gladly make it available here. 
So why don't you reopen this bug *when* qcachegrind is actually available?