From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Chapman Subject: Re: [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list Date: Thu, 12 Jun 2008 22:42:15 +0100 Message-ID: <48519837.1090902@katalix.com> References: <1209577322.25560.402.camel@pmac.infradead.org> <200806102235.09598.rob@landley.net> <484F66F8.4020409@snapgear.com> <200806111941.51221.rob@landley.net> <20080612182529.GB7423@nibiru.local> <485190E8.80705@cisco.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <485190E8.80705@cisco.com> Sender: linux-embedded-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: David VomLehn Cc: weigelt@metux.de, Linux Embedded Maillist David VomLehn wrote: > Enrico Weigelt wrote: >> * Rob Landley schrieb: >> >>> Cross compiling breaks stuff, yes. >>> >>> Most packages don't cross compile at all. Debian has somewhere north >>> of 30,000 packages. Every project that does large scale cross >>> compiling (buildroot, gentoo embedded, timesys making fedora cross >>> compile, etc) tends to have about 200 packages that cross compile >>> more or less easily, another 400 or so that can be made to cross >>> compile with _lot_ of effort and a large enough rock, and then the >>> project stalls at about that size. >>> >> >> The problem is: most embedded projects don't make really general-purpose >> fixes (instead strange things like hacking up autogenerated files), so >> they can't feed back to upstream. >> >> IMHO, a huge waste of working time. >> >> > Amen, brother. I'm fortunate in that I work for an organization that is > quite good about enforcing code reviews, specifically, the QA > organization is empowered to reject changes that do not have code review > notes. I also have a fairly broad scope, so I'm in on code reviews for a > number of open source components. At each such review, one of my > criteria is whether the change is suitable for pushing back to the > appropriate community. This is not necessarily a short-term way to make > friends, but the long-term effects will be good both for the company and > for the open source community in general. > > Now, if we can only get the time to actually push all the backlogged > fixes out... Er, is that GPL or LGPL code that you're modifying? If so, you *have* to push those code changes out (make them available to others), whether you think people will be interested or not! > -- > David VomLehn, dvomlehn@cisco.com > The opinions expressed herein are likely mine, but might not be my > employer's... -- James Chapman Katalix Systems Ltd http://www.katalix.com Catalysts for your Embedded Linux software development