On Thu, 2010-07-01 at 11:39 +0100, Andrew Flegg wrote:
> On Thu, Jul 1, 2010 at 11:00, Patrick Ohly <[email protected]> wrote:
> > On Thu, 2010-07-01 at 10:31 +0100, Konrad Zapalowicz wrote:
> >> I guess it will be released in October
> >> http://meego.com/developers/meego-roadmap
> >
> > It is possible to build your own chroot by following the instructions
> > here:
> > http://wiki.meego.com/Building_a_MeeGo_chroot_on_Linux
> >
> > I've done it recently, using a Netbook boot image with the Handset bits.
> 
> What's the development environment of those working on the Handset UX;
> how are they managing to do development; and how do they get new
> employees up to speed quickly?

I used the Wiki instructions, which got me started fairly quickly (less
than half a day?). But I'm not a new employee and already knew the basic
steps.

>  I imagine they don't point to the image
> creator or the chroot instructions and say "figure it out from there";
> so that there should be *some* collateral allowing people to get up to
> speed more quickly? (Hopefully!)

I don't know. I could have asked, but going through the Wiki
instructions was a worthwhile experiment by itself, so I did that
instead.

I guess if you have someone hand-holding you (as it would be the case
for a new on-site employee), then there are easier ways, like simply
copying a full chroot. Externally we'll need something more sustainable
- in other words, SDKs.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to