I have read the section on not using dependencies (http://docs.octopusdeploy.com/display/OD/Packaging+applications) and I agree but I think we're missing a nice feature if we consider dependencies as being releases done by Octopus to a given environment that include the nuget that is defined as a dependency. Consider this:

MyOrg.MyApp.Web 1.0.0.0 depends on MyOrg.MyServiceApp.RestApi 1.5.0.0...2.0.0.0.

When I deploy MyOrg.MyApp.Web to environment Production Orcopus could check if I have a release in that environment that deuccessfuly deployed MyOrg.MyServiceApp.RestApi 1.5.0.0...2.0.0.0. Essentially this would make sure all my dependencies between projects are deployed within a given environment.
It could also warn me about incompatibilities between projects when I would deploy MyOrg.MyServiceApp.RestApi 3.0.0.0 to production when I have MyOrg.MyApp.Web expecting a different version.