There's still the issue of how exactly to turn upstream projects into distro packages, which
is often not of any concern to the upstream project and distros don't necessarily make the
same choices. If you've got a project with a bunch of optional parts that each have different
dependencies but are developed together and selected in the upstream distribution at compile
time, it can be unclear how to package this for binary distribution. For example, if you've
got a music player that can optionally support a variety of file formats, but needs a
different external library for each and generates a different binary plugin for each, it's
hard to give a good policy for what goes in the music player package and what goes in add-on
packages. It helps if all of the distros form a consensus is there's no distro-specific policy
reason not to match.