For the purposes of this explanation there are 3 files:
-	control.deb (An empty .deb that only contains DEBIAN/control)
-	existing.deb (A current .deb that resides on a machine with my repo added)
-	new.deb (A new .deb that I wish to “push” to an machine that has my repo added)

	I am attempting to finalize a "push" capability with the current debian repo I maintain.  When I create a new .deb and put it in the repo, I want the other clients to have it "pushed" to them whenever they perform: apt-get update and then an apt-get upgrade.

	The caveat to this is that I want them to have the freedom to be able to do: apt-get --no-install-recommends to avoid having it pushed to them (if they so desire).

	My current method in use is that of where I make sure every person who uses my repo has the following .debs installed: control.deb and existing.deb

	control.deb is an empty .deb in the file structure sense.  Its only purpose it to allow me to manipulate its debian control file for choosing certain things.  Its debian control file has the following line – Depends: existing (=1.0)

	existing.deb and new.deb both have the following line in their debian control file – Depends: control

	I add new.deb to the repo, and change to the following with control.deb’s debian control file – Depends: existing (=1.0), new (=1.0)

	I perform apt-get update && apt-get upgrade and the device now grabs new.deb and installs it.

	This method works; however if the user did not like what new.deb did; and they tried to apt-get remove it, they would receive the warning:
The following packages will be REMOVED:
 existing* control* new*

	In previous experiences with apt-get, sometimes I would want to install a package.  I would do apt-get install foo, and a slew of other packages would appear.  Several google searches later and I learned the apt-get --no-install-recomends install foo technique.
I attempted to implement this with control.deb whereas the debian control file for control.deb had: Recommends: existing (=1.0), new (=.10)

	For this second scenario, I had only control.deb and existing.deb installed.  I performed apt-get update && apt-get upgrade and nothing occurred, it did not “push” the new previously uninstalled package, new.deb to my machine.  Why Not?  How are maintainers able to create packages where --no-install-recommends applies??  What am I doing wrong?