RE: [maemo-developers] Building maemo from cvs
On Fri, 2006-03-31 at 16:40 +0300, [EMAIL PROTECTED] wrote: > > On Fri, 2006-03-31 at 13:51 +0300, [EMAIL PROTECTED] wrote: > > > jhbuild is another beast, i have to learn something about :) > > > Devesh > > > > I think you'll like it. It makes life simple. I should have some > > instructions up on the wiki soon. > > > > I notice that some of the modules in svn (shared-mime-info, > > dbus) don't > > have autogen.sh files, probably because they were added from tarballs. > > But jhbuild needs these files. May I add them, please? (I probably don't have access to do this directly. But it's not complicated for someone else to just copy them from the original cvs modules.) > work with Luc on that > Devesh I've tried. I've had no reply now to three emails about this. Clearly he is far too busy. This is another example of an incredibly simple task/approval stopping contributions. Maemo needs someone who can gets these little blockages out of the way. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
On Mon, 2006-04-03 at 13:51 +0300, Jussi Kukkonen wrote: > Koen Kooi wrote: > > There is a .html file somewhere in stage.maemo.org with list the modules > > + version present in the sdk and fiasco images, which would be real help > > for filling in 1.0. Does anyone remember that URL? > > I believe you mean > http://repository.maemo.org/stable/1.1/package_reference.html What I'd really like to see is some descriptions of the modules. Some of these SVN modules have empty README files. People who know should just edit this wiki page: http://maemo.org/maemowiki/MaemoModules/1%2e1 The experts can fix it later if we get it wrong. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jussi Kukkonen wrote: > 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... And can it a trigger be added to inform http://cia.navi.cx/ so we can have rss feeds and maybe an IRC bot to announce commits? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEMQWYMkyGM64RGpERAp3uAKCH3wqXYfDsh41gfMjLOngIuMwiLQCfalb0 Qw4+svBk7yiflAAH1SkstzU= =yAWY -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
[EMAIL PROTECTED] 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 development. > 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 <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
Koen Kooi wrote: > There is a .html file somewhere in stage.maemo.org with list the modules > + version present in the sdk and fiasco images, which would be real help > for filling in 1.0. Does anyone remember that URL? I believe you mean http://repository.maemo.org/stable/1.1/package_reference.html -- Jussi Kukkonen <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
Hi, > On Sun, 2006-04-02 at 20:34 +0300, [EMAIL PROTECTED] 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. > > Thanks for the reply. > > Could we have at least the names of these software modules, please? Have a look here: https://stage.maemo.org/svn/maemo/projects/haf/hafbuildbot/sources This is the file that drives the build bot I'm playing with. We'll be keeping it up to date until we have something better. I'll try to blog about this today. > > For the modules that are in the public svn, those are all totally > up-to-date, right? For instance, there's not some secret copy of > hildon-libs with extra changes? Yes they are up-to-date There are no secret copies. > > [snip] > > I started a little release planning page, as something to inform the > public development community: > http://maemo.org/maemowiki/MaemoModules > > It would be nice to see it gradually expanded with > - A correct list of modules, with descriptions of those modules. > - Information about approximate development plans and > scheduled freezes. That's a good start :-) > > I can imagine that you don't want to say everything because > it gives too > many clues about product features and launch dates, but > there's probably > a lot that you can say, and it might be acceptable to be very > approximate about dates. Yes, there's some of those concerns. However, most of these components don't carry big secrets, and we're looking at releasing Maemo more frequently than the products. The biggest constrain is quite simple. Prioritization of limited resources ;-) Expect things to happen and to move in the right direction, but to take time. > As well as helping developers and consumers of Maemo to adapt their > plans, this will help us to anticipate the priorities and > stress levels > of Maemo developers at various times. > Yup. Br, Carlos ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Murray Cumming wrote: > [snip] > > I started a little release planning page, as something to inform the > public development community: > http://maemo.org/maemowiki/MaemoModules > > It would be nice to see it gradually expanded with > - A correct list of modules, with descriptions of those modules. > - Information about approximate development plans and scheduled freezes. There is a .html file somewhere in stage.maemo.org with list the modules + version present in the sdk and fiasco images, which would be real help for filling in 1.0. Does anyone remember that URL? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEMOj5MkyGM64RGpERAskJAJ0ZwzMx/cxSrm1xfnI0Wr/E4Kb5XgCeM/V0 rLjAJTPNOu/s3ULEpm/ux40= =HO64 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
On Sun, 2006-04-02 at 20:34 +0300, [EMAIL PROTECTED] 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. Thanks for the reply. Could we have at least the names of these software modules, please? For the modules that are in the public svn, those are all totally up-to-date, right? For instance, there's not some secret copy of hildon-libs with extra changes? [snip] I started a little release planning page, as something to inform the public development community: http://maemo.org/maemowiki/MaemoModules It would be nice to see it gradually expanded with - A correct list of modules, with descriptions of those modules. - Information about approximate development plans and scheduled freezes. I can imagine that you don't want to say everything because it gives too many clues about product features and launch dates, but there's probably a lot that you can say, and it might be acceptable to be very approximate about dates. As well as helping developers and consumers of Maemo to adapt their plans, this will help us to anticipate the priorities and stress levels of Maemo developers at various times. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
Hi, > > 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. > > It would be more productive to let it build from publicly available > sources *only*. Doing so would prevent disaster like multiple packages Yeah, I'm doing that too and that's just fine once you get close enough to the goal and to sustain it. Before that, it helps to throw in the mix some source code from free components not yet in open development to see how they break. And to allow oneself to move on and identify further gaps while waiting for a component to come out rather than getting stuck waiting for it. Anyway, that's more of a methodology issue. The goal is clearly to make sure everything builds fine from publicly available sources only. > needing stuff like mce, which is closed. Making dummy headers > available > like nokia did for mce is a good start. Yeah, that helps. Br, Carlos ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > 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. It would be more productive to let it build from publicly available sources *only*. Doing so would prevent disaster like multiple packages needing stuff like mce, which is closed. Making dummy headers available like nokia did for mce is a good start. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEMBAhMkyGM64RGpERAiyGAKCE3lQYriXq0B8DigkbQgKYAtHFSgCfcD8+ OuKIa95y4ah4s19etWkK3M0= =vDbM -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
Hi, > On Fri, 2006-03-31 at 10:55 +0300, [EMAIL PROTECTED] wrote: > > Murray, > > Such a page would be welcomed. > > > > Few things to consider > > 1. Maemo 1.1 public release usually lag behind internal > product development > > 2. what you see in SVN are realtime in sync (mostly) with > product development > > 3. some of the time, these SVN projects like HAF (hildon > application framework) move on to new components versions or > new dependencies (due to new feature additions) which are not > in Maemo X.X public releases 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. So we're not there. Things are moving incrementally at a pace constrained by the need to work on products as we open up. Murray, Peter and others. Your interest and energy to kick our butts is most appreciated and it makes a difference. 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. Br, Carlos ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
Murray > -Original Message- > From: ext Murray Cumming [mailto:[EMAIL PROTECTED] > Sent: 31 March, 2006 15:21 > To: Kothari Devesh (Nokia-M/Tampere) > Cc: maemo-developers@maemo.org > Subject: RE: [maemo-developers] Building maemo from cvs > > > On Fri, 2006-03-31 at 13:51 +0300, [EMAIL PROTECTED] wrote: > > jhbuild is another beast, i have to learn something about :) > > Devesh > > I think you'll like it. It makes life simple. I should have some > instructions up on the wiki soon. > > I notice that some of the modules in svn (shared-mime-info, > dbus) don't > have autogen.sh files, probably because they were added from tarballs. > But jhbuild needs these files. May I add them, please? work with Luc on that Devesh > > -- > Murray Cumming > [EMAIL PROTECTED] > www.murrayc.com > www.openismus.com > > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
On Fri, 2006-03-31 at 13:51 +0300, [EMAIL PROTECTED] wrote: > jhbuild is another beast, i have to learn something about :) > Devesh I think you'll like it. It makes life simple. I should have some instructions up on the wiki soon. I notice that some of the modules in svn (shared-mime-info, dbus) don't have autogen.sh files, probably because they were added from tarballs. But jhbuild needs these files. May I add them, please? -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of ext Murray > Cumming > Sent: 31 March, 2006 12:45 > To: Kothari Devesh (Nokia-M/Tampere) > Cc: maemo-developers@maemo.org > Subject: RE: [maemo-developers] Building maemo from cvs > > > On Fri, 2006-03-31 at 10:55 +0300, [EMAIL PROTECTED] wrote: > > Murray, > > Such a page would be welcomed. > > > > Few things to consider > > 1. Maemo 1.1 public release usually lag behind internal > product development > > 2. what you see in SVN are realtime in sync (mostly) with > product development > > 3. some of the time, these SVN projects like HAF (hildon > application framework) move on to new components versions or > new dependencies (due to new feature additions) which are not > in Maemo X.X public releases > > > > So to build from scratch (i am throwing things from my head now :) > > 1. get a empty scratchbox > > 2. get a basic developer rootstrap from public maemo release > > 3. set up the apt/sources.list to target the Maemo x.x repository > > Ah, so is more than one set of packages in that repository? How can I > discover which are available. I currently have this in my > sources.list: > > deb http://repository.maemo.org/ maemo1.1rc5 free non-free > deb-src http://repository.maemo.org/ maemo1.1rc5 free deb http://repository.maemo.org/ maemo1.1 free non-free deb-src http://repository.maemo.org/ maemo1.1 free > > If we can get recent builds of the code currently being > worked on, then > that helps a lot, but we will still need to build from cvs > too (usually > to a separate prefix). For instance, many of the GNOME Developer use > Ubuntu's unstable release (with the latest GNOME as released in > tarballs) but also use jhbuild to develop the software that > can go into > the tarballs. Mostly what i am talking is a bootstrap process to bleed edge unstable development. once you have that (which makes you reach a point where all basic development dependencies are satisfied), and keeps a clean development environment and process, then you can start pulling from SVN's and CVS's of the components you want to hack So what I am outline is more of your unstable Maemo because Maemo yet dont have it :) that is like ubuntu's unstable. > > > 4. set up a local repository on host system(i prefer using > a localhost webserver), something like maemo unstable [this > is where all the new and updated components used by e.g HAF would go] > > So you are talking here about a .deb/apt package repository > here rather > than a svn repository? Yes I meant apt/deb repository > > > 5. Look into e.g HAF SVN and find (thats the hard part), > all the new dependencies introduced and updated components. > If the project itself dont provide them , then grab them from > mainstream and put them in local repo. It would really help is projects like HAF would have some kind of release process, which also outlines the build process together with the dependencies and their versions. > > Yes, this is something that the jhbuild modulesets should > show. I'd also > like to see a page like this, with the module list for a > certain release > phase, with branch names: > http://live.gnome.org/TwoPointFifteen/Platform > > > 6. Give your local repo preference over the Maemo repo. > [you can use tools like apt-ftparchive stuff to create you a > Packages.gz/Sources.gz etc] > > 7. apt-get update, install etc > > 8. get the latest SVN source, and then I think you have > possibility of some success :) > > 9. once you create and compiled you packages from SVN > sources, upload them to you local repository. > > This local apt repository only seems necessary in order to load the > updated software onto the device. For working in scratchbox > and xephyr, > it does not seem necessary. Well it also keeps your development environment sane, and easy to reproduce e.g you move to another SB configuration etc. > > > 9. To test : Grab developer rootfs from Maemo , and flash to device > > 10. setup USB networking and modify the apt/sources.list to > also point to your local repo, and then the magic apt > dist-upgrade (who knows, it might work, at least the theory > sound reasonable, isnt it ?) > > > > Now here I am assuming when you say Maemo from scratch, you > mean Hildon Application Framework, which is in my terminology > just HAF, which sits on top of "Maemo Core" [which is all > base system, X, gdk, gtk, gconf etc etc] > > Well, when we build the hildon-* libs, we also need to build Maemo's > custom GTK+ version, for instance, so I t
RE: [maemo-developers] Building maemo from cvs
On Fri, 2006-03-31 at 10:55 +0300, [EMAIL PROTECTED] wrote: > Murray, > Such a page would be welcomed. > > Few things to consider > 1. Maemo 1.1 public release usually lag behind internal product development > 2. what you see in SVN are realtime in sync (mostly) with product development > 3. some of the time, these SVN projects like HAF (hildon application > framework) move on to new components versions or new dependencies (due to new > feature additions) which are not in Maemo X.X public releases > > So to build from scratch (i am throwing things from my head now :) > 1. get a empty scratchbox > 2. get a basic developer rootstrap from public maemo release > 3. set up the apt/sources.list to target the Maemo x.x repository Ah, so is more than one set of packages in that repository? How can I discover which are available. I currently have this in my sources.list: deb http://repository.maemo.org/ maemo1.1rc5 free non-free deb-src http://repository.maemo.org/ maemo1.1rc5 free If we can get recent builds of the code currently being worked on, then that helps a lot, but we will still need to build from cvs too (usually to a separate prefix). For instance, many of the GNOME Developer use Ubuntu's unstable release (with the latest GNOME as released in tarballs) but also use jhbuild to develop the software that can go into the tarballs. > 4. set up a local repository on host system(i prefer using a localhost > webserver), something like maemo unstable [this is where all the new and > updated components used by e.g HAF would go] So you are talking here about a .deb/apt package repository here rather than a svn repository? > 5. Look into e.g HAF SVN and find (thats the hard part), all the new > dependencies introduced and updated components. If the project itself dont > provide them , then grab them from mainstream and put them in local repo. Yes, this is something that the jhbuild modulesets should show. I'd also like to see a page like this, with the module list for a certain release phase, with branch names: http://live.gnome.org/TwoPointFifteen/Platform > 6. Give your local repo preference over the Maemo repo. [you can use tools > like apt-ftparchive stuff to create you a Packages.gz/Sources.gz etc] > 7. apt-get update, install etc > 8. get the latest SVN source, and then I think you have possibility of some > success :) > 9. once you create and compiled you packages from SVN sources, upload them to > you local repository. This local apt repository only seems necessary in order to load the updated software onto the device. For working in scratchbox and xephyr, it does not seem necessary. > 9. To test : Grab developer rootfs from Maemo , and flash to device > 10. setup USB networking and modify the apt/sources.list to also point to > your local repo, and then the magic apt dist-upgrade (who knows, it might > work, at least the theory sound reasonable, isnt it ?) > > Now here I am assuming when you say Maemo from scratch, you mean Hildon > Application Framework, which is in my terminology just HAF, which sits on top > of "Maemo Core" [which is all base system, X, gdk, gtk, gconf etc etc] Well, when we build the hildon-* libs, we also need to build Maemo's custom GTK+ version, for instance, so I think it makes sense to call it Maemo. I'm having some success with building HAF via jhbuild at the moment. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Building maemo from cvs
Murray, Such a page would be welcomed. Few things to consider 1. Maemo 1.1 public release usually lag behind internal product development 2. what you see in SVN are realtime in sync (mostly) with product development 3. some of the time, these SVN projects like HAF (hildon application framework) move on to new components versions or new dependencies (due to new feature additions) which are not in Maemo X.X public releases So to build from scratch (i am throwing things from my head now :) 1. get a empty scratchbox 2. get a basic developer rootstrap from public maemo release 3. set up the apt/sources.list to target the Maemo x.x repository 4. set up a local repository on host system(i prefer using a localhost webserver), something like maemo unstable [this is where all the new and updated components used by e.g HAF would go] 5. Look into e.g HAF SVN and find (thats the hard part), all the new dependencies introduced and updated components. If the project itself dont provide them , then grab them from mainstream and put them in local repo. 6. Give your local repo preference over the Maemo repo. [you can use tools like apt-ftparchive stuff to create you a Packages.gz/Sources.gz etc] 7. apt-get update, install etc 8. get the latest SVN source, and then I think you have possibility of some success :) 9. once you create and compiled you packages from SVN sources, upload them to you local repository. 9. To test : Grab developer rootfs from Maemo , and flash to device 10. setup USB networking and modify the apt/sources.list to also point to your local repo, and then the magic apt dist-upgrade (who knows, it might work, at least the theory sound reasonable, isnt it ?) Now here I am assuming when you say Maemo from scratch, you mean Hildon Application Framework, which is in my terminology just HAF, which sits on top of "Maemo Core" [which is all base system, X, gdk, gtk, gconf etc etc] Hope that helps Cheers Devesh > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of ext Murray > Cumming > Sent: 29 March, 2006 20:42 > To: maemo-developers@maemo.org > Subject: [maemo-developers] Building maemo from cvs > > > Is there any documentation anywhere about building (and using) maemo > from svn, installed in a separate prefix, or should I start a new page > on the maemo wiki? > > -- > Murray Cumming > [EMAIL PROTECTED] > www.murrayc.com > www.openismus.com > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
On Thu, 2006-03-30 at 09:13 +0100, Peter Robinson wrote: [snip] > It also means that you don't need to do funky things > like install a parallel install of dbus in /usr/local and do funky > things with shell env vars to get pkgconfig to find it! What a strange coincidence that you should mention that. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
> > > Is there any documentation anywhere about building (and using) maemo > > > from svn, installed in a separate prefix, or should I start a new page > > > on the maemo wiki? > > > > Along this track is there a apt where you can use a rawhide style > > system running the latest builds of maemo from svn? > > That'd be fantastic too. Like using either Ubuntu's Stable or Unstable > repositories. > > I guess it would need resources though. If Nokia need a justification > for this, it should be increased testing. It's great to hear almost > immediately when your changes have broken something. Well, it's better > than hearing about it later. It also makes it easier for devs who are writing software that needs the newer libs that would probably be in the newer release allowing for extra software to be available essentially the same time as a new major release. It also means that you don't need to do funky things like install a parallel install of dbus in /usr/local and do funky things with shell env vars to get pkgconfig to find it! Peter Peter ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
On Wed, 2006-03-29 at 18:45 +0100, Peter Robinson wrote: > > Is there any documentation anywhere about building (and using) maemo > > from svn, installed in a separate prefix, or should I start a new page > > on the maemo wiki? > > Along this track is there a apt where you can use a rawhide style > system running the latest builds of maemo from svn? That'd be fantastic too. Like using either Ubuntu's Stable or Unstable repositories. I guess it would need resources though. If Nokia need a justification for this, it should be increased testing. It's great to hear almost immediately when your changes have broken something. Well, it's better than hearing about it later. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building maemo from cvs
> Is there any documentation anywhere about building (and using) maemo > from svn, installed in a separate prefix, or should I start a new page > on the maemo wiki? Along this track is there a apt where you can use a rawhide style system running the latest builds of maemo from svn? Peter ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
