I emerged kdevelop-php, and it took me a while to figure out why I couldn't launch it. It's a plugin for kdevelop, but it doesn't have a depend in the ebuild, so I had to emerge it separately. Shouldn't any plugin depend on the thing in plugs into? Reproducible: Always Steps to Reproduce: 1. emerge kdevelop-php without kdevelop already emerged 2. 3. Actual Results: kdevelop-php emerges, but does not pull in kdevelop. Expected Results: kdevelop would be pulled in as a dependency.
Not really, kdevelop is not the only host for this plugin. The other is Quanta (which is in development now).
It doesn't make sense to install a plugin without something to plug into. Is there a way to test for either host? If neither is installed, then it could use a USE flag to specify which is wanted, or perhaps even just fail and tell the user one or the other (php-develop or quanta) has to be installed first.
Other USE case is that you only have kdevplatform + plugins installed from Portage, and kdevelop manually compiled (if you're contributor for instance). What you're requesting is unnecessary complexity imho.
I'd suggest an elog msg like: if ! has kdevelop || quanta: elog "you don't seem to have a host for this plugin, consider installing kdevelop or quanta"
To Comment 3: Isn't that what package-provided is for? I really don't want to add complexity, but as a user, I expect the portage system to tell me what I need to be able to use a package, either by pulling it in as a dependency (possibly controlled by USE flags if I actually have some choice), or by at least giving me a message before or after emerging. To Comment 4: While I would prefer it actually pulls in one or the other (or fails if you haven't specified which, such as by USE flag) I would find that message quite acceptable.
Maciej, are you OK with the elog or should we resolve it?
This discussion makes no sense. 1) If you install kdevelop by hand, you are on your own. And, true, that is what package.provided is for. 2) Right now we have no ebuild for quanta anywhere. RDEPEND added in tree and overlay...
The RDEPEND for kdevelop-php-docs doesn't seem to be new. I don't see the point of DEPEND for kdevelop-pg-qt, and I don't think that's what you were referring to, was it? I also don't get your point about being on my own for installing kdevelop manually. I emerged it, why should I be on my own? I would understand that if I did configure, make, make install, but that's not what I did. package.provided would be useful if I had manually installed kdevelop or quanta, but I have not done that. I'm not going to bother to reopen, but I really don't understand the resistance to having kdevelop-php depend on kdevelop.
