Hi there, I just checked this with kid3-0.10, but I suspect this also happening with other versions of the tool. The problem is that kid3 won't build without kde libs installed. I looked through their homepage and KDE support is optional, only the QT libraries are needed. I have installed qt4 through portage, but kid3 fails to build. So I looked into the ebuild and found out that it seems to force the installation on the KDE libs, although not needed. The ebuild even talks about that the configure step tries to detect them. That's not entirely correct. I did grab the kid3-0.10 myself, unpacked them and running the ./configure script in the base directory indeed fails because it can't find the kde-config tool. BUT changing into the kid3-qt subdir and doing ./configure && make there I managed to build a perfectly working kid3 executable. No problems with missing KDE libs, or kde-config stuff. I think the ebuild maintainer might have overlooked something here, or do I miss something here? Thanks, Tobias
Reopen with complete emerge log and emerge --info output; thanks.
Created attachment 146796 [details] emerge --info output
Created attachment 146798 [details] ACCEPT_KEYWORDS="~x86" emerge -vp kid3 output
Created attachment 146800 [details] ./configure output when exec in kid3-0.10 base-dir
Comment on attachment 146800 [details] ./configure output when exec in kid3-0.10 base-dir KDE libs are not installed, only qt4 libs
Created attachment 146802 [details] ./configure output when exec from kid3-0.10/kid3-qt subdir again KDE libs are not present, only QT4 libs are installed - the config process exits succesfully
(In reply to comment #1) > Reopen with complete emerge log and emerge --info output; thanks. > I attached the emerge --info and some other build logs, but not the emerge log, which is illogical anyway. As already said the app builds with portage, BUT only when kde libs are installed. So it wants to pull in the kde stuff, which I don't want and which is NOT required. Should I post the compile log when compiling kid3-0.10 by hand? I have only uploaded the ./configure step log.
I'd say something's rather wrong with the kde eclasses when they don't force kdelibs dependency... Doesn't make any sense.
But this here is not about KDE. Read the requirements on http://kid3.sourceforge.net/: There it says: "and runs under Linux (KDE or only Qt) and Windows" only Qt! Which is totally correct and proven when using the kid3-qt build directory and not the basedir. The current ebuild enforces installation on KDE stuff because it sees a dependency where no one is.
It definitely does depend unconditionally on KDE 3.5, my understanding is that the reporter would like to see this being optional.
Are there any ebuilds depending on kid3? Perhaps we could have a virtual/kid3 if it is needed and a pair media-sound/kid3-qt media-sound/kid3-kde, both defaulting to qt3 and kde3.5 respectively, and having a qt4 and kde4 USE flags for selecting which version of the toolkits/frameworks to build against. The INSTALL file on the recent 1.0 version tells: *** Compile for KDE # if configure does not exist: make -f Makefile.cvs ./configure # for SuSE use option --prefix=/opt/kde3 # for Debian use option --prefix=/usr make make install The install directory can be assigned to DESTDIR *** Compile for KDE 4 cmake -DCMAKE_INSTALL_PREFIX=/usr/lib/kde4/ . make make install *** Compile for Qt (no KDE) cd kid3-qt # if configure does not exist: autoconf ./configure make make install The install directory can be assigned to INSTALL_ROOT *** Compile for Qt 4 cd kid3-qt ./configure --with-qmake=qmake-qt4 make make install It looks simple. Any suggestions? I could upload te corresponding ebuild if needed.
Hi i created kid3 for kde4/kde3 based on what user has around :] But problem is that it wont compile with kde headers, it have me lots of warnings and app has some issues when running then. So closing as wontfix. If you find anyone else willing to spare some time on that fee free to reopen or create new bugreport.
