https://bugzilla.novell.com/show_bug.cgi?id=722152
https://bugzilla.novell.com/show_bug.cgi?id=722152#c3
--- Comment #3 from Jonathan Schmidt-Dominé
- how we name the packages comes from our own policies.
I do not know your policies, I just want to mention that KDevelop-PG-Qt and KDevelop are completely independent programs (though sharing developers and users), KDevelop-PG-Qt is not related to version 4 of KDevelop. Using kdevelop4-pg-qt as a name is kinda like konq4uest for the game Konquest because of Konqueror 4 (although that is an exaggeration ;), you can of course name it however you think it should be like).
- You do not explain why there should not be a -devel package.
If you want to use the binary you will also need the headers (to clarify the behaviour: the binary will run without them, but the output will be useless, the output uses the headers). The headers are not for accessing KDevelop-PG-Qt as a library.
Currently, these headers are required at build time by (at least): - kdev-java, - kdev-php, - kdev-qmake
Yes, but the binary is used as well, both are needed for building the plugins. Bad formulation by me, the binary does not use it as kinda data, but using the binary implies using the headers. Why should I post it to a mailing list? Regards Jonathan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.