[rlpb]

That's a very selective quote. You failed to quote the very next sentence: "But we can see the benefits of encouraging developers to factor both Ubuntu and Debian into their packaging efforts, so we're open to that."

> This is in contrast with Canonical refusing to build packages for Debian...

False, as demonstrated by reading the full quote. There is no refusal there, just resource allocation in sorting out the infrastructure.

[m_rcin]

OK, it was a selective quote and there was no refusal. Ubuntu developers just want to fix first all the bugs that matter for Ubuntu users (which is as distant now as 5 years ago, in practice it's the same as refusal).

So there is a contrast. Ubuntu devs haven't made what would be a nice gesture toward their upstream distro. OTOH SUSE provides resources for building packages for several unrelated distros.

[rlpb]

> Ubuntu devs haven't made what would be a nice gesture toward their upstream distro.

They make nice gestures toward their upstream distro all the time, just not this one, for which they have said that code contributions are welcome. 3913 nice gestures (in the form of patches) are logged at http://udd.debian.org/cgi-bin/ubuntu_usertag.cgi, for example.

> OTOH SUSE provides resources for building packages for several unrelated distros.

Sure, and Ubuntu has chosen to focus contributions in other areas. I think that's perfectly reasonable.

One issue here is that the build infrastructure around Launchpad is (presumably) designed around securely building packages for a single distribution. To support other distributions, it seems to me that it would need some mechanism for users to supply their own chroots, or some other way of maintaining those chroots. This is quite different from the Debian builder model, which is designed around third party build contributions. I imagine (I don't know) that this affects the amount of effort required to make this all work on Launchpad. Remember that PPA support was added in later, not present from the start (http://blog.launchpad.net/ppa/personal-package-archives-for-... looks like the original announcement).

On the other hand, as far as I understand SUSE designed their system to be able to handle several unrelated distros from the beginning. That presumably made it easier for them to do it.

I don't think it's fair to complain that X won't expend resources on something but Y will, when the amount of resource required by X and Y may differ quite considerably.

[ewzimm]

Especially since replicating Open Build Service would be a waste of effort. It already exists. There doesn't need to be a Canonical version of it. If someone wants to build a package for multiple distros, use Open Build Service. Launchpad serves a different purpose.