Editing Mer/Build/Processes

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

== OBS Project structure and promotion ==

The Mer projects on OBS look like this:
 Maemo:Mer:Stable
 Maemo:Mer:Stable:HW:Beagle
 Maemo:Mer:Stable:HW:N8x0

This means all devices will have the main 'Stable' repository and an appropriate HW repository.

The development area is expanded slightly:
 Maemo:Mer:Devel:Apps
 Maemo:Mer:Devel:Base
 Maemo:Mer:Devel:MaemoCommon
 Maemo:Mer:Devel:MaemoCommon:L10n
 Maemo:Mer:Devel:UI
 Maemo:Mer:Devel:HW:Beagle:Devel
 Maemo:Mer:Devel:HW:N8x0:Devel

Details of packages in each area is given in the[[Mer/Packages|Packages]] pages.

Packages in each of these Devel subproject areas can be hacked on and then, when they're kinda working they are consolidated into the :Devel area (which is used as a build target for the :Devel:* subprojects)
 Maemo:Mer:Devel
 Maemo:Mer:Devel:HW:N8x0
 Maemo:Mer:Devel:HW:Beagle

Packages are placed in :Testing with the intention of including
them in the next release subject to QA and bug fixes

Maemo:Mer:Testing
  Maemo:Mer:Testing:HW:Beagle
  Maemo:Mer:Testing:HW:N8x0

Once :Testing is ready a release of all packages to a numbered version is made:
  Maemo:Mer:0.13
  Maemo:Mer:0.13:HW:Beagle
  Maemo:Mer:0.13:HW:N8x0

Note that the :HW promotion process is slightly different:
 Maemo:Mer:Devel:HW:N8x0:Devel -> Maemo:Mer:Devel:HW:N8x0 -> Maemo:Mer:Testing:HW:N8x0 -> Maemo:Mer:Stable:HW:N8x0

=== Promotion Tasks ===

To promote a package:
  osc copypac <SOURCEPRJ> <SOURCEPAC> <DESTPRJ>
eg:
  osc copypac -k Maemo:Mer:Devel glib2.02 Maemo:Mer:Testing
The <code>-k</code> ensures that the maintainer info is preserved.

Ensure that:
  osc meta prjconf <SOURCE>
is copied to the <TARGET> conf. This may contain things like package selection preferences.
Currently the prjconf is:
 Prefer: hildon-fm-l10n-mr0
 Ignore: hildon-fm-l10n-mr
 Prefer: notify-osd
 Ignore: initramfs:initramfs-tools,udev,blueman
 Ignore: libmbca0:bluez-gnome
 Ignore: libgtk2.0-common:libgtk2.0-0
 Ignore: libgtk2.0-bin:libgtk2.0-0
 # Added following for claws-mail. "have choice for libdb-dev needed by libetpan-dev: libdb4.2-dev libdb-dev"
 Prefer: libdb-dev

== To Promote :Devel To :Testing ==

First pipe over the project metadata:
  osc meta prjconf Maemo:Mer:Devel  | osc meta prjconf Maemo:Mer:Testing -F -

Then run:
  for i in $(osc ls Maemo:Mer:Devel); do echo $i; osc copypac Maemo:Mer:Devel $i Maemo:Mer:Testing ; done
  for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
    for i in $(osc ls Maemo:Mer:Devel:$HW); do echo $i; osc copypac -k Maemo:Mer:Devel:$HW $i Maemo:Mer:Testing:$HW ; done
  done

== To Promote :Testing to :Stable ==

The process here is to create a versioned repo; eg :0.14

export STABLE=0.14
  export OLD=0.13

Create the projects (copied from $OLD):
  osc meta prj Maemo:Mer:$OLD | sed "s/$OLD/$STABLE/" |osc meta prj Maemo:Mer:$STABLE -F -
  for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
    osc meta prj Maemo:Mer:$OLD:$HW | sed "s/$OLD/$STABLE/" |osc meta prj Maemo:Mer:$STABLE:$HW -F -
  done

Pipe over the project metadata:
  osc meta prjconf Maemo:Mer:Testing  | osc meta prjconf Maemo:Mer:$STABLE -F -

Then run:
  for i in $(osc ls Maemo:Mer:Testing); do echo $i; osc copypac Maemo:Mer:Testing $i Maemo:Mer:$STABLE ; done
  for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
    for i in $(osc ls Maemo:Mer:Testing:$HW); do echo $i; osc copypac -k Maemo:Mer:Testing:$HW $i Maemo:Mer:$STABLE:$HW ; done
  done

Then, once it's built and stable, use _aggregate to link each package to :Stable

First clean out :Stable
  for i in $(osc ls Maemo:Mer:Stable); do echo $i; osc rdelete Maemo:Mer:Stable $i ; done
  for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
    for i in $(osc ls Maemo:Mer:Stable:$HW); do echo $i; osc rdelete Maemo:Mer:Stable:$HW $i; done
  done

*** ALSO wipebinaries next time ***

NOTE The following uses -m in osc which is not accepted upstream yet. It will not work unless you have lbt's osc patches.

for i in $(osc ls Maemo:Mer:$STABLE); do echo $i; osc aggregatepac Maemo:Mer:$STABLE $i Maemo:Mer:Stable; done
  for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
    for i in $(osc ls Maemo:Mer:$STABLE:$HW); do echo $i
      osc aggregatepac -m MerStable_Debian_5.0=Mer${STABLE}_Debian_5.0,MerStable_Ubuntu_9.04=Mer${STABLE}_Ubuntu_9.04 Maemo:Mer:${STABLE}:$HW $i Maemo:Mer:Stable:$HW
    done
  done

Note that :Stable project must be setup to publish and to build

== Linking to :Extras ==
In order to allow people to develop applications/packages for :Extras they need to setup their home area on OBS as in [[Mer/Build/Building Applications|Building Applications]]. Once the package is built it can be linked to Maemo:Mer:Extras:Devel
  osc linkpac -f -c home:tomaszd84 leafpad Maemo:Mer:Extras:Devel

<code>-c</code> ensures that the version is pinned so when user tomaszd84 changes his package, it doesn't change in :Extras:Devel unless it is relinked.
<code>-f</code> forces an existing link to be updated.

== Linking ==

To link to a source create a _link file containing:
  <link project="linked project name" package="linked package name">

optionally:
  <patches>
    <apply name="name of the first patch" />
  </patches>

Sadly these patches apply to the files in the source; so this means you need to apply the diff to the maemo-ised diff file.

[[Category:Mer]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Ambox (view source) (semi-protected)
Template:Mer (view source) (semi-protected)

Retrieved from "http://wiki.maemo.org/Mer/Build/Processes"

Personal tools

Navigation

Views

Editing Mer/Build/Processes

@@ Line 1: / Line 1: @@
-{{Mer}}
 == OBS Project structure and promotion ==
@@ Line 50: / Line 48: @@
 Ensure that:
-<nowiki>
    osc meta prjconf <SOURCE>
-</nowiki>
 is copied to the <TARGET> conf. This may contain things like package selection preferences.
 Currently the prjconf is:
@@ Line 69: / Line 65: @@
 First pipe over the project metadata:
    osc meta prjconf Maemo:Mer:Devel  | osc meta prjconf Maemo:Mer:Testing -F -
-Clean out :Testing
-  for i in $(osc ls Maemo:Mer:Testing); do echo $i; osc rdelete Maemo:Mer:Testing $i ; done
-  for HW in HW:N8x0 HW:N900 HW:SmartQ HW:Freerunner HW:Beagle; do
-    for i in $(osc ls Maemo:Mer:Testing:$HW); do echo $i; osc rdelete Maemo:Mer:Testing:$HW $i; done
-  done
 Then run:
-  osc wipebinaries --all Maemo:Mer:Testing
    for i in $(osc ls Maemo:Mer:Devel); do echo $i; osc copypac Maemo:Mer:Devel $i Maemo:Mer:Testing ; done
-   for HW in HW:N8x0 HW:N900 HW:SmartQ HW:Freerunner HW:Beagle; do
+   for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
-    osc wipebinaries --all Maemo:Mer:Testing:$HW
      for i in $(osc ls Maemo:Mer:Devel:$HW); do echo $i; osc copypac -k Maemo:Mer:Devel:$HW $i Maemo:Mer:Testing:$HW ; done
    done
@@ Line 94: / Line 81: @@
 Create the projects (copied from $OLD):
    osc meta prj Maemo:Mer:$OLD | sed "s/$OLD/$STABLE/" |osc meta prj Maemo:Mer:$STABLE -F -
-   for HW in HW:N8x0 HW:N900 HW:SmartQ HW:Freerunner HW:Beagle; do
+   for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
      osc meta prj Maemo:Mer:$OLD:$HW | sed "s/$OLD/$STABLE/" |osc meta prj Maemo:Mer:$STABLE:$HW -F -
    done
@@ Line 103: / Line 90: @@
 Then run:
    for i in $(osc ls Maemo:Mer:Testing); do echo $i; osc copypac Maemo:Mer:Testing $i Maemo:Mer:$STABLE ; done
-   for HW in HW:N8x0 HW:N900 HW:SmartQ HW:Freerunner HW:Beagle; do
+   for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
      for i in $(osc ls Maemo:Mer:Testing:$HW); do echo $i; osc copypac -k Maemo:Mer:Testing:$HW $i Maemo:Mer:$STABLE:$HW ; done
    done
-Allow to build.
-<hr>
 Then, once it's built and stable, use _aggregate to link each package to :Stable
@@ Line 115: / Line 98: @@
 First clean out :Stable
    for i in $(osc ls Maemo:Mer:Stable); do echo $i; osc rdelete Maemo:Mer:Stable $i ; done
-   for HW in HW:N8x0 HW:N900 HW:SmartQ HW:Freerunner HW:Beagle; do
+   for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
      for i in $(osc ls Maemo:Mer:Stable:$HW); do echo $i; osc rdelete Maemo:Mer:Stable:$HW $i; done
    done
@@ Line 124: / Line 107: @@
    for i in $(osc ls Maemo:Mer:$STABLE); do echo $i; osc aggregatepac Maemo:Mer:$STABLE $i Maemo:Mer:Stable; done
-   for HW in HW:N8x0 HW:N900 HW:SmartQ HW:Freerunner HW:Beagle; do
+   for HW in HW:N8x0 HW:SmartQ HW:Freerunner HW:Beagle; do
      for i in $(osc ls Maemo:Mer:$STABLE:$HW); do echo $i
        osc aggregatepac -m MerStable_Debian_5.0=Mer${STABLE}_Debian_5.0,MerStable_Ubuntu_9.04=Mer${STABLE}_Ubuntu_9.04 Maemo:Mer:${STABLE}:$HW $i Maemo:Mer:Stable:$HW
@@ Line 136: / Line 119: @@
 == Linking to :Extras ==
-In order to allow people to develop applications/packages for :Extras they need to setup their home area on OBS as in [[Mer/Build/Application_Building|Building Applications]]. Once the package is built it can be linked to Maemo:Mer:Extras:Devel
+In order to allow people to develop applications/packages for :Extras they need to setup their home area on OBS as in [[Mer/Build/Building Applications|Building Applications]]. Once the package is built it can be linked to Maemo:Mer:Extras:Devel
    osc linkpac -f -c home:tomaszd84 leafpad Maemo:Mer:Extras:Devel
@@ Line 153: / Line 136: @@
 Sadly these patches apply to the files in the source; so this means you need to apply the diff to the maemo-ised diff file.
+[[Category:Mer]]