Mer: Difference between revisions

From Maemo Wiki
Jump to navigationJump to search
imported>stskeeps
New page: == Blueprint for Mer == === Launchpad page === http://launchpad.net/m-r === Platforms targeted === * hasty-armv5el * hasty-armv5el-vfp * hasty-armv6el-vfp * jaunty-armel * jaunt...
 
imported>stskeeps
No edit summary
Line 1: Line 1:
== Blueprint for Mer ==
== Blueprint for Mer ==


Line 18: Line 17:
Repositories at http://trac.tspre.org/mer/<arch>
Repositories at http://trac.tspre.org/mer/<arch>


* stable - stable release, packages are througly tested and work on all platforms
  * stable - stable release, packages are througly tested and work on all platforms
* testing - where packages that build on all platforms and has passed general testing
  * testing - where packages that build on all platforms and has passed general testing
* unstable - where built packages are entered at first, packages may not be same on all platforms.
  * unstable - where built packages are entered at first, packages may not be same on all platforms.
   
   
=== Branching from Maemo packages ===  
=== Branching from Maemo packages ===  


* get bzr-svn, bzr
  * get bzr-svn, bzr
* bzr branch <svn-url>
  * bzr branch <svn-url>
* bzr push bzr+ssh://username@bazaar.launchpad.net/~username/m-r/<package name>
  * bzr push bzr+ssh://username@bazaar.launchpad.net/~username/m-r/<package name>


=== Builder system ===  
=== Builder system ===  
Line 33: Line 32:


Requests: http://jaiku.com/channel/merbuilder
Requests: http://jaiku.com/channel/merbuilder
Authorized users (identified by their login) can ask builder by sending <platform regexp> <bzr branch url> to start building on archs matching the platform regexp. For example, jaunty-* lp:~carsten-munk/m-r/glib


=== Build system ===  
=== Build system ===  


beagle1: BeagleBoard handling source, hasty-{armv5el,armv5el-vfp,armv6el-vfp}, jaunty-armel
  * beagle1: BeagleBoard handling source, hasty-{armv5el,armv5el-vfp,armv6el-vfp}, jaunty-armel. Location: Århus, DK
dell1: pentium4 handling jaunty-i386
 
  * dell1: pentium4 handling jaunty-i386. Location: Århus, DK

Revision as of 18:31, 20 November 2008

Blueprint for Mer

Launchpad page

http://launchpad.net/m-r

Platforms targeted

* hasty-armv5el
* hasty-armv5el-vfp
* hasty-armv6el-vfp
* jaunty-armel
* jaunty-i386

Repositories and branches

Repositories at http://trac.tspre.org/mer/<arch>

 * stable - stable release, packages are througly tested and work on all platforms
 * testing - where packages that build on all platforms and has passed general testing
 * unstable - where built packages are entered at first, packages may not be same on all platforms.

Branching from Maemo packages

 * get bzr-svn, bzr
 * bzr branch <svn-url>
 * bzr push bzr+ssh://username@bazaar.launchpad.net/~username/m-r/<package name>

Builder system

Status: http://merbuilder.jaiku.com

Requests: http://jaiku.com/channel/merbuilder

Authorized users (identified by their login) can ask builder by sending <platform regexp> <bzr branch url> to start building on archs matching the platform regexp. For example, jaunty-* lp:~carsten-munk/m-r/glib

Build system

 * beagle1: BeagleBoard handling source, hasty-{armv5el,armv5el-vfp,armv6el-vfp}, jaunty-armel. Location: Århus, DK
 * dell1: pentium4 handling jaunty-i386. Location: Århus, DK