Configure class library for NuGet distribution

Question

I am investigating how I can use NuGet to distribute developer frameworks and tools within my organization. I have the server setup and am able to generate packages and add them to consuming projects. I am now looking to expand this into a more real-world situation.

In my case, I will have a framework that we distribute to all of the development teams in the organization. This framework has a "core" class library then a set of technology-specific libraries such as Acme.Web, Acme.Silverlight and so on. Each of these libraries references the "core" assembly.

I have packaged each of these assemblies into it's own NuGet package including "core" which is set as a dependency within the other packages. This is because developers may chose to only reference "core" when creating class libraries but also want those types when creating web apps, etc.

The other idea is that I could release a new version of my "core" assembly without requiring updates in all of the other packages. Or can I?

Imagine the case where I have project A, add NuGet package B that has a dependency on NuGet package C then package C is updated. Is it possible to distribute this update without rebuilding, repackaging and reposting package B? If so, are there any steps I need to take to ensure there are no versioning issues?