Q: I have made some fixes and/or changes. How do I submit them?

A: Just email your modifications to genkdesvn-discussion@lists.sourceforge.net

Q: What about qt-copy (qt-3.99)?

A: If you emerge qt-3.99, it will be used for further compilation, otherwise qt-3* will be used. qt-3.99 installs into /usr/qt/devel, let me know if you experience problems with it. In short, unlike kdelibs-7, nothing enforces installation of qt-3.99, you need to install it yourself. Also, if you know that any of the ebuilds work with older versions of kdelibs, let me know so I can lower their requirements, so people don't have to install the svn kdelibs, but use their release version if they want the independent package. At present only koffice and non-distro ebuilds (amarok, konversation, etc.) have lower requirements.

Q: How do I know when to update, if there are no revision numbers to these ebuilds?

A: There is a script in the repositoy (scripts/updateKDEsvn) that checks for each installed KDE-svn app, if a newer revision exists on SVN, and then only compiles and installs if a newer revision exists.

Q: I am installing package A, but I see that package B is also being compiled! Why?

A: Many modules are interdependent. Part of the difficulty of maintaining subversion ebuilds is tracking all the changes and newly added dependencies. Feel free to play with the corresponding variables in the ebuild, until you reduce some of the (sometimes heavy) dependencies. Here are some variables that you might want to concentrate on:

• KMCOMPILEONLY - everything listed here will be compiled, but not installed.
• KMEXTRACTONLY - everything listed here will be extracted, but not compiled, nor installed
• KMEXTRA - everything listed here will be compiled and installed (you are more likely to add to this, as this is mostly used for combined packages i.e. *-data, etc., and not as dependency handling)