Request for best practices for resolving dependencies in my PPA

I'm working on wrapping my brain around using a PPA to build packages I require for work but that are not current in gutsy.

The problem that I've encountered is satisfying dependencies. (Of course) I'm attempting to build the latest Anjuta, for example, which requires two dependencies in universe. This builds just fine in pbuilder, since I've got universe enabled. I'd like to know the "soyuz" way to resolve these dependencies in my PPA.

My understanding is that I must build these packages in my PPA _first_, so that they are available in the Xen sbuilder.

My naive attempt to resolve them went something like this:

1 -- I checked the build output for "does not exist" when satisfying dependencies, and found two that were unavailable. (In the future I would check this out before dputing the changes, but I didn't this time because pbuilder worked just fine.)

2 -- For each of these dependencies I did an "apt-get source package" to get the latest source.

3 -- Inside each dependency I did a "dch -i" and noted that it was a repack for my PPA.

4 -- Then a "debuild -S -sa" and a debsign on the changes files for the dependency.

5 -- I dput the dependencies to my PPA and waited for them to finish building.

6 -- I navigated to the failed build and used the portlet to "retry the build".

It's still pending/building, so maybe that didn't fix it, but I've got a moment to ask the question and wanted to get the opinion of experts before I beat my head into my keyboard!

So the final question: is this the best way to resolve these dependencies?

Thanks!