MVC package structure question

Forgive the slightly vague thread title, but I’m struggling with finding info on this because I can’t seem to phrase my queries right.

Simply:

Usually I have separate packages for model, view and controller. This however presents a recurring dilemma. I want my controllers to be more intimate with the model than the views, because they should operate more directly on its data. Take for instance a scrollbar. The controller would take pixel values from the graphic elements and translate them into ratios for the model to store. It might be that the controller then needs access to properties in the model that I don’t want exposed to the views. Having separate packages will force me to present the same interface to controllers and views, but I don’t want to stuff all controllers in the model package and use the internal access modifier either, because then that becomes messy after a while.

Anyone else pondered this question?