[maemo-developers] [maemo-developers] Building maemo from cvs

From: Jussi Kukkonen jhkukkon at cc.hut.fi
Date: Mon Apr 3 14:15:17 EEST 2006
Carlos.Guerreiro at nokia.com wrote:
> Yup. We've been little by little moving components to open
> development in the stage svn but still not everything required
> to build Maemo (or even the HAF) from source (at the most
> current releases) is available. There's still some way to go.
> We've been considering and experimenting with various options for
> adapting and opening up our internal development processes to
> allow the community to follow the bleeding edge and get involved.
> We realize that this is a serious barrier making it too hard for
> people to get involved now, the regular stable Maemo releases
> are not sufficient. Access to the source code in development is
> obviously a key part of that. But that's not enough. People also
> need bleeding-edge (unstable) packages in sync with the source on
> svn, in a repository they can track with apt, and much more.

I'd like to specifically mention the public bugzilla as something that
could be improved. At the moment it more resembles a customer feedback
channel than a real tool that could be used to follow "the lifespan of a
bug/enhancement". This is another hindrance to getting familiar with the

> On a related issue, I've been for some time tracking the move
> to open development of the HAF through a build bot working
> (mostly) from publicly available sources, in order to identify
> and address the gaps. I'll post some info on that soon.

Great, looking forward to it.
 On a somewhat related note: Would it be a bad idea if the maemo-commits
mailing list posts included the full diff?  Following the changes via
the list is currently a little tedious since it requires constantly
changing from email-app to browser and back...

Jussi Kukkonen
<jhkukkon at cc.hut.fi>

More information about the maemo-developers mailing list