Hello, please could you look after that circular dependencies in quake4 ebuild. Thx, Jj USE flag: cdinstall # emerge -av quake4-bin These are the packages that would be merged, in order: Calculating dependencies... done! !!! Error: circular dependencies: ebuild / games-fps/quake4-bin-1.3.2 merge depends on ebuild / games-fps/quake4-data-1.0.2147.12 merge (hard) ebuild / games-fps/quake4-data-1.0.2147.12 merge depends on ebuild / games-fps/quake4-bin-1.3.2 merge (hard)
This new circular dependency detection sucks... especially since there's no way to say "yes, these packages both depend on each other for runtime, but this one should be installed first" in an ebuild. Anyway, I'll "fix" this by removing the dependency from one of them and putting in a warning note.
Fixed now in CVS
(In reply to comment #1) > This new circular dependency detection sucks... especially since there's no way > to say "yes, these packages both depend on each other for runtime, but this one > should be installed first" in an ebuild. If you do one as a PDEPEND, then it will be treated as a soft dependency, which means that a circular dep will be okay and the merge order will not be strictly enforced.
Thanks, Zac. Sorry if I seem a little dense, but I would only list it as PDEPEND, or both RDEPEND *and* PDEPEND? Should I do both as PDEPEND, or pick one to be RDEPEND and one PDEPEND, fex. quake4-data would PDEPEND quake4-bin and quake4-bin would RDEPEND quake4-data?
(In reply to comment #4) > Sorry if I seem a little dense, but I would only list it as PDEPEND, or both > RDEPEND *and* PDEPEND? If you do both, then the RDEPEND will still be treated as a hard dep as for as portage is concerned, so the PDEPEND would be rendered useless. > Should I do both as PDEPEND, or pick one to be RDEPEND > and one PDEPEND, fex. quake4-data would PDEPEND quake4-bin and quake4-bin > would RDEPEND quake4-data? Either one of those will work. As long as they don't both RDEPEND on eachother you should be fine.
Ideally on a fresh install, the -data ebuild would be triggered to install first, so that -bin can be downloading in the background while -data is installing from the CD :)
That is exactly what it does (provided you have USE=cdinstall, anyway) now. Thanks again, Zac!
