Seems if you have both the .5x and .6x versions of gstreamer/plugins it defaults to using gst-inspect from the .5x series. On my machine it made the whole merge crap out, patch is attached to fix...
Created attachment 10948 [details, diff] Makes configure look for gst-inspect
mhmm i don't follow really, both 0.5 and 0.6 should have a versioned gst-inspect. Only early (non portage) versions of gst-0.5 are unversioned (which is not my problem ofcourse). And how does it crap out, these are i suppose the tests for certaing plugins, but they shouldnt hinder the building. They are just warning to my knowledge.
On my system it complains rather loudly about not having the cdparanoia plugin
in case it cant find certain plugins it may break, i'm not sure. But on a gentoo system this should never really happen, cause it can't find our gst-inspect and ignores the checks it seems. Did you or did you not use a gst-0.5 ebuild not from the portage tree i wonder ? And about the checks, well.. we can't force use flags atm, so there is no good way to make sure certain plugins get built. I'm thinking about dividing up plugins at some point in the future to make this possible, but that's not really relevant here.
I'm about %90 percent sure I used the "official" ebuild, but it has been a while since I installed (2003-01-27 09:37). All this patch does is make sure configure looks for gst-inspect-0.6 instead of just gst-inspect. That way it will find whatever plugins are installed. To clarify, I have the cdparanoia plugin installed but the configure script doesn't find that I do. This patch fixes that.
this only happens because it finds gst-inspect (which in your case 0.5 without versioning, unlike it is in portage) and 0.5 doesnt have the cdparanoia plugin. 0.6.1 has cdparanoia as include and will install it, so changing to gst-inspect-0.6 fixes it for you. If you have both 0.5 and 0.6 versioned, the config script won't find gst-inspect and ignores the tests alltogether. Which is the way i prefer it.
Why in the world is it better to ignore the tests??? Seems to me the author put em in for a reason, and I'm guessing they will become blockers but oh well.. I tried...
my facts checking puppet liquidx kindly pointed out i never backported versioning to 0.5 guess i have to fix the configure after all still i will disable the checks, we can't force dependencies on gst-plugins so there is no way to make sure plugins are there.
Why disable the checks? Isn't it better for someone to find out before wasting time emerging that things aren't right on their system for this package? I realize there's no way to "force dependancies" for the plugins, but at least the config file should catch the missing plugins. If disabling all the tests in the config file is just "The Way", then I would think a pkg_setup test for the needed libs would be a good idea...
no, i don't want to knowingly possibly break an ebuild, while it isn't necessary.
fixed now
