On Tue, Oct 4, 2011 at 2:08 PM, Tom Swindell <t.swind...@rubyx.co.uk> wrote:
> On Tue, 2011-10-04 at 13:58 +0200, Jeremiah Foster wrote: > > On Tue, Oct 4, 2011 at 11:35 AM, Sivan Greenberg <si...@omniqueue.com> > > wrote: > > On Tue, Oct 4, 2011 at 11:28 AM, Carsten Munk > > <cars...@maemo.org> wrote: > > > Long story short: buildd and launchpad is very useful but > > only when > > > you're doing Debian and Debian only. > > > > > > Except it was built by Canonical for Ubuntu and is used by Linaro. But > > perhaps those two things are "Debian" too? > > > > OBS is different in many > > > different ways and allows a proper productization > > environment as well > > > as growing an organisation organically. > > > > > > > > What does that even mean? > > OBS is built with packaging in mind, so it builds packages locally and > on servers in a sanitized environment. Scratchbox may be polluted by > whatever packages a developer has installed and makes dependency > tracking a bit harder IMO. > I agree that working in a dirty chroot is problematic. That is why there is pbuilder and cowdancer. > > I think what Carsten means by "growing an organisation organically" is > that OBS allows multiple users to create their own repositories, it > allows us to separate different projects into different repositories for > staging or logical separation and it's easy and intuitive to do all of > this from the web interface and to tools provided. > This is likely what he's referring to. But as someone who is concerned with integration, this is bordering on a misfeature. What is happening is that each repository is a separate Linux distro. This makes integration a complete nightmare and unlikely to occur. Look a the ABI break that occurred in MeeGo for ARM. That effectively killed any release of that distro. Just because you can build your own Linux distro doesn't mean you should. > > OBS may not offer anything more or less than Launchpad or buildd, but it > is completely open source and it targets many more distributions than > Launchpad or buildd do. > And more package formats, processor virtualization, per-package compiler flags, and a mock version control tool, etc. But all these things can mean that your package will not work with other distros and then we are back to everyone doing their own thing. How does that help move free software forward? It doesn't, it only encourages the silo effect and Not Invented Here. Before it was just big companies that could create their own Linux distros (before that everyone had their bespoke UNIX distro) nowadays fragmentation is brought to you by every Tom, Dick and Harry with an OBS login. I've been down the fragmentation road before. It always ends with retracing your path back to the main highway. Regards, Jeremiah
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
