Hi Guys, there's a problem with the current stable mythtv ebuild (0.20.1_p14146) the ebuild pulls in mythtv-themes as a dep, but the themes depend on mythtv itself. when you "emerge mythtv" it pulls in mythtv-themes which throws this error: "Project ERROR: run ./configure". Not particularly helpful, espc considerin this is the output from the configure script ;) I've had a look at the configure, and it needs some files from a ready-built mythtv. I've found a forum post for this dating back to january.. I'm getting around it by:- # emerge mythtv # emerge --resume --skipfirst # emerge mythtv-themes Reproducible: Always Steps to Reproduce: 1. emerge -C mythtv mythtv-themes 2. emerge mythtv 3.
Stuff needed at compile time is DEPEND, nor RDEPEND. Fixed summary accordingly.
This is proper as per the PDEPEND discussions with the Portage people. beandog has just created a brand new MythTV box from scratch and had 0 problems installing it. I installed mythtv on my desktop and had 0 problems emerging it. You provided no emerge --info, which is required with every bug. jakub, isn't that you deal to make sure we get that? With regard to the error message, "Project ERROR: run ./configure". That is coming directly from MythTV's scripts, why don't you complain to them about the lack of details or info.
Doug and I talked about it earlier today .. apparently its portage changing behavior with PDEPEND. Solution for now? Just emerge mythtv first (emerge -O mythtv) then mythtv-themes aterwards.
If mythtv-themes need mythtv at emerge time, just change RDEPEND to DEPEND. "PDEPEND <-> DEPEND" loops CAN be solved by portage.
I committed this when Steve and I talked earlier. It's already done.
