snip >> >> If people agree that this is a good idea, the next question would be >> >> where to >> >> host it - is this something that could be within the meta-oe repository? >> >> >> > Grabbing all of these barely supported machines into their own layer sounds >> > like a good plan to me. >> > >> > Id suggest just hosting it on gitorious, if its inside OE then there is the >> > magic assumption from the public that they should work (which is what >> > happens >> > now). Then people get really dissapointed when I tell them getting it to >> > work >> > is likely to be a hard slog. >> >> I agree with Graeme on the hosting bit. I also have all the devices you >> mentioned near my desk, so testing should be easy :) > > I'm going to disagree, this is exactly the kind of layer fragmentation > I'd not like to see layers cause. Which website do I go to where I can > see a list of layers that exist? Who is going to maintain that list? If > its off on gitorious nobody will be able to easily find it. > > The easiest solution is if git.openembedded.org or git.yoctoproject.org > can host the majority of the meta-* repositories. > > Equally, I don't really see why this can't be a specific meta- group in > meta-oe. The README can clearly spell out what the expectations of the > layer are... > > Cheers, > > Richard
I agree with Richard, for keeping it as meta- group. About expectations, at least for Zaurus I don't see problems: vanilla 2.6.38 kernel, actual udev, imminent move to xorg-xserver if kdrive is finally doomed. Ipaq's seem suffering more bitrot... Andrea _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
