PPA dependencies are presented in the PPA page for any user, badly but they are.
The central question here is whether we should always include them in the 'sourceslist' widget or not.
I'm still thinking that build dependencies are not necessary in run time for most of the cases, but one alternative would be to let the PPA owner decide this aspect when he adds a new dependency.
{{{
...
Add PPA *build* dependency: [ ] (Choose…) [ ] also needed in run-time
Extra dependencies: [ ] PPA for James Henstridge (run-time) [ ] PPA for Foo Bar [ ] PPA for Biscuit
<Save> or Cancel
}}}
Unrelated, but it would also be interesting to see which PPAs depends on the PPA you are viewing.
PPA dependencies are presented in the PPA page for any user, badly but they are.
The central question here is whether we should always include them in the 'sourceslist' widget or not.
I'm still thinking that build dependencies are not necessary in run time for most of the cases, but one alternative would be to let the PPA owner decide this aspect when he adds a new dependency.
{{{
...
Add PPA *build* dependency: [ ] (Choose…) [ ] also needed in run-time
Extra dependencies: [ ] PPA for James Henstridge (run-time)
[ ] PPA for Foo Bar
[ ] PPA for Biscuit
<Save> or Cancel
}}}
Unrelated, but it would also be interesting to see which PPAs depends on the PPA you are viewing.