Do workspaces support sub-projects relative referencing other subprojects?

[Taytay]

I'm not sure I'm using Rye correctly. I've got a workspace and subprojects A and B and C.

C depends on B. B depends on A.

During development this works because all projects are installed in the venv.

But when I build the wheel for a given project it didn't include the sibling projects because I forgot to declare the dependency.

So I went into project B and declared a --path dependency on ../A

But that adds a dependency on an absolute path that gets copied into the wheel, and of course doesn't work at install time in my docker container.

I found this:
#912

I'm not sure if I'm even doing the right thing by trying to declare these relative dependencies? How do I ensure that the wheel or package gets the right source code included of the correct subset of workspace projects?

I am new to python packaging in general and am surprised that monorepos aren't a more common scenario. I love rye and its simple approach, so I feel like I'm missing something!

Any help appreciated.

[Taytay]

Slightly related question:
I want to make sure each of my subprojects explicitly declare their package dependencies out of the global universe of installed packages in my root venv because if I don't, the wheel won't include them, and it crashes at runtime.
That's why I thought I needed to also declare my relative project dependencies...

But I've also found this issue in hatch: pypa/hatch#1261

And that makes me think I might need to force include the other package folders?

[Taytay]

Here's the hack I've used to support declaring these references in a more explicit way such that the dependencies are pulled in at the appropriate times:
#615 (comment)