I came here to the support site prior to bothering bioc-devel, but searching for "circular dependencies" cf. https://github.com/Bioconductor/Contributions/blob/master/CONTRIBUTING.md#submitting-related-packages did not surface any answers that seemed relevant. This seems like it might be a recurrent issue, though, so if anyone can document best practices for [the following, it would be great]:
1) providing a Data package (let's call it MTseekerData, because that's its name) holding data structures where
2) the S4 class data structures are generated from a package (let's call it MTseeker, because that's its name), and
3) the package (MTseeker) requires the MTseekerData package and the latter must be submitted as a GitHub issue first, but the package wants to autoload the MTseeker software package as part of its installation (even though I don't import it, to try and avoid this), and thus without some finagling, the full battery of examples, vignette steps, and tests cannot run for the MTseeker software package.
OK, now off to email@example.com and bioc-devel, but hopefully this question can avoid other people doing the same.
Any answers here are much appreciated, and I'll add responses from Lori and/or bioc-devel as they come in.
[edited for grammar, edits in brackets]