tracker will not build without a gtk-doc.make file in the ${S} directory. However, there is no such file provided by the svn repository. I solved this by copying a gtk-doc.make file from thunar over into the portage working directory, but I think there has to be a better solution. Reproducible: Always Steps to Reproduce: 1. emerge tracker Actual Results: Failed tracker-9999 compilation. Error message in automake output: "Cannot open < gtk-doc.make" Expected Results: tracker-9999 successfully compiled. dev-util/gtk-doc is not installed. dev-util/gtk-doc-am-1.10-r1 is installed. Compilation works after copying gtk-doc.make into ${S}.
Thanks for reporting this problem; assigning to maintainer.
needs to call gtkdocize of gtkdoc-prepare before eautoreconf.
seems like a fix was found for this: "Compilation works after copying gtk-doc.make into ${S}." and "needs to call gtkdocize of gtkdoc-prepare before eautoreconf." however, not sure what either of these mean :) sorry, new Gentoo user. is it possible to get the new ebuild? thanks.
a) Why is this in tree? This belongs in the gnome-live.git overlay b) ebuild has not been updated for the move to git c) ebuild has not been updated /at all/ => This needs to be updated and moved to the overlay. This has no place in the tree
(In reply to comment #4) > a) Why is this in tree? This belongs in the gnome-live.git overlay > b) ebuild has not been updated for the move to git > c) ebuild has not been updated /at all/ > > => This needs to be updated and moved to the overlay. This has no place in the > tree > thanks, got it. will look into the gnome overlay for latest tracker.
(In reply to comment #5) > (In reply to comment #4) > > a) Why is this in tree? This belongs in the gnome-live.git overlay No, why? It duplicates patches and makes combined maintenance a mess. My vote against it and for closing as INVALID. Updating the build is a different story. If you can use help from me on that, please contact me.
will track necessary changes with bug #269928 *** This bug has been marked as a duplicate of bug 269928 ***