On a practical note, we are forced to maintain these 2 packages separately if only because Ubuntu uses upstart and Debian doesn't.
Re: network effects of Ubuntu dependencies. In our case that was not a factor, since Docker is a static binary built in Go, and all distros are equally hapless in their management of that. In fact, we are divorcing ourselves completely from distro-specific dependency management. As of this week, docker packages are built by us in an environment we control, not the distro build farms (hint: we build docker with docker). Then we wrap it with fpm and call it a day. Separately, we are working with downstream maintainers of each distro to help them package docker in a policy-compliant way. But those are 2 completely separate tracks.
- A. nearly every developer uses Ubuntu on their own workstations, and
- B. Ubuntu has all the other shiny new pre-1.0 stuff to pull in as deps (it's a network effect, in other words.)
So, would, say, slapping Ubuntu's apt repo-set into Debian work to satisfy an Ubuntu-targeted DEB's prerequisites, or would there be tons and tons of conflicts?