[Dev] orphan-packaging model

Lv, RuiX ruix.lv at intel.com
Thu Sep 4 03:12:54 GMT 2014

Hi Patrick,

The convert action only create the orphan packaging branch which only contains packaging info. 
Thus, you need to create the corresponding development branch that contains libphonenumber source code with `gbs devel start`.

Please follow the following procedure, I've verified it on my side.

1. Clone the package and switch to it.

$ git clone tizen: platform/upstream/libphonenumber
$ cd libphonenumber
$ git br
* accepted/tizen_common

2. Convert to orphan-packaging model
1) Create packaging branch.
$ gbs devel convert
$ git br 
* accepted/tizen_common-orphan
2) Create development branch
$ gbs devel start
$ git br
* development/accepted/tizen_common-orphan/5.3.2

3. Do development on development branch and export patches to packaging branch.
# Do local development.
$ gbs devel export
$ git br
* accepted/tizen_common-orphan

4. Commit patches and perform building.
$ git add * 
$ git commit -s 
$ gbs build -A i586


-----Original Message-----
From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of Patrick Ohly
Sent: Thursday, September 04, 2014 12:05 AM
To: dev at lists.tizen.org
Subject: [Dev] orphan-packaging model


Is anyone already using the orphan-packaging model (https://source.tizen.org/documentation/reference/git-build-system/maintenance-models-supported-gbs)?

I tried converting an existing package (libphonenumber) to that new model with "gbs devel convert", but the result was that "gbs build"
failed to build on the development branch (couldn't find sources).

I've probably done something wrong. Currently I am trying to start from scratch. I found the documentation a bit lacking. It just says what branches must exist, without explaining what files need to be created and committed there. A HOWTO showing the steps that are necessary would be useful.

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.

Dev mailing list
Dev at lists.tizen.org

More information about the Dev mailing list