Nuget convincing that I came across a dependency on another package

I have a project where I would like to use https://www.nuget.org/packages/Bootstrap.Datepicker/ , so being a good modern developer I suggest VS add this nuget package. Which is cool. But along with that comes Bootstrap 2.3.1, which I know is a dependency of that package. But my project already has Bootstrap Less Source package (3.2.0.1) installed and I am concerned about having two different "instances" of "the same" package in my project. Another developer on my team pointed out that any Nuget packages that are download based might need the default default rather than the same source package we are using, although that works best for us.

Is there a way in nuget to tell it to ignore dependencies, or to convince it that instead of the expected dependency, it is encountered differently?