Strictly speaking, the yum distributor shouldn't reach over into the yum importer.

More generally, plugins should be independent of each other. The only cross over is supported types. So now matter how the RPMs got into a repo, either from the yum importer or Bob's RPM Importer, the yum distributor should be able to publish them.

That's the purist theory. You're not committing any heinous sins here (we have in the past) in terms of coupling the two. For instance, the yum importer used to put things in a location that the yum distributor would use, meaning anyone wanting to use the yum distributor on its own would have to know about that outside contract.

In this case, it means we wouldn't be able to package the yum importer and distributor separately. That's not likely to happen anytime soon, so it's not a huge deal. I mostly mention it to make sure you heard the strict design spiel. It's your call if you cant to pull that constant out to somewhere in common.