On 8/13/2010 8:28 PM, Alistair Buxton wrote: > > The problem is I don't know how to tell OBS to rebuild all the > packages without using prebuilt Meego RPMs to do it - all the > existing documentation is geared towards someone who wants to build a > single package against an already bootstrapped distro.
Not wearing my Collabora, Freedesktop, Ubuntu, or Debian hats here, but I've given some thought in the past (and more, as I've seen this discussion rage on) to doing a "baseline 686" (or even 586, but gcc's 586 targets aren't as well-tested these days as they used to be) MeeGo port just to help get more community developers on board and the like. Yes, I understand the arguments of others that it will lack certainly whizz-bangery, and be less optimal on my Atom-based netbook, and I don't much care. I can still run it, and I can develop for it, and I can run the optimized version, should that tickle my fancy. I'd need to scare up some resources (perhaps with work, perhaps within the community at large) to make it happen, but from the rampant me-too-ing going on here, it looks like it would be a project that would actually see some use, even by people I work with (hi Robin). Just so people who don't know who I am realize I'm not jumping into a thread to blow smoke up various backsides, I did porting to several architectures in Debian for years, I bootstrapped Ubuntu's LPIA (y'know, before Atom had a name) and ARM ports when I worked at Canonical, and this sort of work is more or less in my blood. And hey, if it would stop my INBOX from being flooded by list mail, I'm all for it. ... Adam (Seriously, though, can I wake up to this thread not having expanded by another 200 mails? My list-reading OCD is going to kill my weekend) _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
