m |
|||
| (14 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | The Community OBS is | + | See also [http://wiki.meego.com/Getting_started_with_OBS Getting started with OBS] |
| + | |||
| + | The Community OBS ([https://build.pub.meego.com/ https://build.pub.meego.com/]) is now part of meego.com infrastructure and supports several important kinds of development: | ||
| + | |||
| + | * Applications to run on MeeGo | ||
| + | * Surrounds: the MeeGo contribution and sharing area | ||
| + | * Team Repositories | ||
| + | * Personal Repositories | ||
| + | |||
| + | Having these areas allow us to support: | ||
| + | * Extras : MeeGo's community App store complete with QA via Extras:Testing | ||
| + | * Managing packages as part of their acceptance into MeeGo core | ||
| + | * Deprecating packages from MeeGo core | ||
| + | * A high quality distribution built around MeeGo core | ||
| + | |||
| + | = TOC = | ||
| + | (some ideas on scope - probably an intro and a link to a sub-page) | ||
| + | * Prerequisites (links to other resources like SDK) | ||
| + | * Getting access to the OBS | ||
| + | * Local installation (cover general and distro variations) | ||
| + | * Learning to use it (tutorials) | ||
| + | * Organising projects: Best practice and team usage (including branches, building against other prj) | ||
| + | * [[Build_Infrastructure/Community_Builder/Tips_and_tricks|Tips and tricks]] (bind mounts for git in local builds; cross-compiles; other clever tricks) | ||
| + | * What the Targets are for? | ||
| + | * Fremantle, Harmattan and others | ||
| + | * New architectures (armv5 or MIPS anyone?) | ||
| + | * [[Build_Infrastructure/Community_Builder/Common_pitfalls|Common pitfalls]] | ||
| + | |||
| + | == Getting Access == | ||
| + | |||
| + | The current (Jan2011) mechanism for getting access is : you ask lbt/X-fade on irc and explain what you plan to do; you tell them your meego account; they say "done"... you sign in. | ||
| + | |||
| + | You use the credentials from www.meego.com. | ||
| + | |||
| + | People ask why it's not just wide open: | ||
| + | * We have limited resources (as yet we have 5 workers) and this keeps us aware of usage | ||
| + | * we had someone wanted to rebuild all MeeGo on armv6 ... but hadn't spoken to the arm porters | ||
| + | * some other people wanted to do closed source and didn't realise the "OSI approved licenses only" policy | ||
| + | * irc is a good captcha | ||
| + | |||
| + | It takes an hour for passwd changes to sync (ie on the hour, every hour). If you created a new account on meego.com, please wait an hour before requesting access. This will ensure the account has been synchronized to the community OBS. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | stuff below is old and can be removed | ||
| + | ---- | ||
The current version co-exists with the Maemo.org OBS and targets: | The current version co-exists with the Maemo.org OBS and targets: | ||
| Line 6: | Line 51: | ||
The plan is to add: | The plan is to add: | ||
* MeeGo:Current:Core : Always points to the latest release snapshot | * MeeGo:Current:Core : Always points to the latest release snapshot | ||
| - | * MeeGo:1.0.80.1.20100514.1:Core : each weekly snapshot. See [[ | + | * MeeGo:1.0.80.1.20100514.1:Core : each weekly snapshot. See [[Release_Engineering/Release_Versioning|the release guidelines]] for an explanation of the numbering. |
The deployment supports home:<user> based building only at the moment. | The deployment supports home:<user> based building only at the moment. | ||
| Line 35: | Line 80: | ||
* manish, embedded hw-sw developer, want to work on meego applications and make it work for arm devices, eager to run it on gumstix and smartq devices, can build and cross compile, but new to OBS | * manish, embedded hw-sw developer, want to work on meego applications and make it work for arm devices, eager to run it on gumstix and smartq devices, can build and cross compile, but new to OBS | ||
* leo0916, embedded system SE, want to port meego to the different device, I need to build some midware to fix some problem, Now I work on the devkit8000. | * leo0916, embedded system SE, want to port meego to the different device, I need to build some midware to fix some problem, Now I work on the devkit8000. | ||
| + | * [http://meego.com/users/fabo Fathi Boudra/fabo] Debian/KDE/MeeGo developer/maintainer | ||
| + | |||
| + | (all accounts above enabled 19 Nov 2010... from now on just ask lbt/x-fade on irc or via email - also, please help document the process) | ||
| + | |||
| + | [[Category:Build Infrastructure]] | ||
See also Getting started with OBS
The Community OBS (https://build.pub.meego.com/) is now part of meego.com infrastructure and supports several important kinds of development:
Having these areas allow us to support:
(some ideas on scope - probably an intro and a link to a sub-page)
The current (Jan2011) mechanism for getting access is : you ask lbt/X-fade on irc and explain what you plan to do; you tell them your meego account; they say "done"... you sign in.
You use the credentials from www.meego.com.
People ask why it's not just wide open:
It takes an hour for passwd changes to sync (ie on the hour, every hour). If you created a new account on meego.com, please wait an hour before requesting access. This will ensure the account has been synchronized to the community OBS.
stuff below is old and can be removed
The current version co-exists with the Maemo.org OBS and targets:
The plan is to add:
The deployment supports home:<user> based building only at the moment.
Community OBS Testing Volunteers
If you want to help with the development and/or testing of the community OBS please add your details below and ensure you contact lbt/X-fade on irc :-
(all accounts above enabled 19 Nov 2010... from now on just ask lbt/x-fade on irc or via email - also, please help document the process)