Bug 148721 – audacious-1.2.0_rc1 ebuild lacks sufficient RDEPENDS

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Karsten Baumgarten 2006-09-22 17:28:33 UTC]

The build order is wrong when emerging audacious-1.2.0_rc1, since the ebuild lacks sufficient RDEPENDS (like those in earlier versions). It has a PDEPEND on audacious-plugins, which would pull in some (all?) of the required packages, but that's too late for compiling audacious itself. A simple workaround is to use the RDEPENDS of an earlier version of the ebuild (I used audacious-1.1.2-r1.ebuild).

REPRODUCIBLE: yes, by emerging audacious-1.2.0_rc1
WORKAROUND  : add RDEPENDS (see above)

[Comment 1 Jakub Moc (RETIRED) 2006-09-22 17:32:19 UTC]

Sorry, this doesn't make much sense. Reopen with some errors and emerge --info, or explain better what's your problem. audacious can't DEPEND on its plugins, that would only produce a circular dependency.

[Comment 2 Karsten Baumgarten 2006-09-23 01:22:21 UTC]

Uhm...you got me wrong here. I did not mention a dependency for audacious on its plugins, but rather a PDEPEND contained in its ebuild (which is just fine, because we want audacious-plugins to be merged after audacious). The problem is NOT the _P_DEPEND, but the missing packages in _R_DEPEND in the audacious ebuild. It was there in previous versions of the ebuild. If you emerge audacious-1.2.0_rc1, it'll show up as the first package to be merged (granted that you have the packages installed, which the ebuild specifies in RDEPEND). Please see Bug #148729 for the error that arises due to this problem.

[Comment 3 Jakub Moc (RETIRED) 2006-09-23 01:40:34 UTC]

Marking as duplicate. if you mean something else, then finally post the error messages, because you still didn't explain your problem.


*** This bug has been marked as a duplicate of 148729 ***

[Comment 4 Karsten Baumgarten 2006-09-23 01:58:45 UTC]

Oh well, I guess commenting on that would just lead to nothing but a rant. Marking it as a duplicate is just fine...