(Checkout half; checkin to come soon.) |
(→Summary and next steps) |
||
| (6 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | = How to use the MeeGo / OBS Command Line | + | = How to use the MeeGo / OBS Command Line Tools, Part 2 = |
You've used the set up the 'osc' tool in [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|Part 1]] and now it's time to check out your project for local editing and build. | You've used the set up the 'osc' tool in [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|Part 1]] and now it's time to check out your project for local editing and build. | ||
| Line 5: | Line 5: | ||
== Find the project to checkout == | == Find the project to checkout == | ||
| - | You can list projects you can check out using ' | + | You can list projects you can check out using 'osc ls'. You will see your home project you created in the Web UI listed too: |
| - | $ | + | $ osc ls |
| - | + | Trunk | |
| - | + | Trunk:Testing | |
| - | + | devel:base | |
| - | + | ||
| - | + | ||
| - | + | ||
... | ... | ||
home:<login> | home:<login> | ||
... | ... | ||
| - | + | ||
== Change to your OBS area == | == Change to your OBS area == | ||
| Line 29: | Line 26: | ||
This is a lot like using Subversion or CVS as the model is 'checkout' and 'checkin' (abbreviated 'co' and 'ci', respectively): | This is a lot like using Subversion or CVS as the model is 'checkout' and 'checkin' (abbreviated 'co' and 'ci', respectively): | ||
| - | $ | + | $ osc co home:<login> |
A home:<login> | A home:<login> | ||
A home:<login>:bash | A home:<login>:bash | ||
| Line 36: | Line 33: | ||
You will now find your checked out project ready for modification and rebuild under home:<login>/<packagename> | You will now find your checked out project ready for modification and rebuild under home:<login>/<packagename> | ||
| + | |||
| + | == Branching a package to your home project == | ||
| + | |||
| + | If using MeeGo OBS: | ||
| + | |||
| + | $ osc branch Trunk:Testing <packagename> | ||
| + | |||
| + | Tips, use 'bco' subcommand alias will make osc checkout the branched package meanwhile: | ||
| + | |||
| + | $ osc bco Trunk:Testing <packagename> | ||
== Summary and next steps == | == Summary and next steps == | ||
This guide gave an introduction on how to use the osc tool to checkout sources. | This guide gave an introduction on how to use the osc tool to checkout sources. | ||
| - | The next page will cover building your project. Click [[Build_Infrastructure/Packagers_Developers/CLI_Part_3| | + | The next page will cover building your project. Click [[Build_Infrastructure/Packagers_Developers/CLI_Part_3|here]] to open the 3rd part. |
[[Category:Build Infrastructure]] | [[Category:Build Infrastructure]] | ||
Contents |
You've used the set up the 'osc' tool in Part 1 and now it's time to check out your project for local editing and build.
You can list projects you can check out using 'osc ls'. You will see your home project you created in the Web UI listed too:
$ osc ls Trunk Trunk:Testing devel:base ... home:<login> ...
Create a directory for doing work and change directory into it:
$ mkdir ~/obs $ cd ~/obs
This is a lot like using Subversion or CVS as the model is 'checkout' and 'checkin' (abbreviated 'co' and 'ci', respectively):
$ osc co home:<login> A home:<login> A home:<login>:bash A home:<login>:bash/Makefile ...
You will now find your checked out project ready for modification and rebuild under home:<login>/<packagename>
If using MeeGo OBS:
$ osc branch Trunk:Testing <packagename>
Tips, use 'bco' subcommand alias will make osc checkout the branched package meanwhile:
$ osc bco Trunk:Testing <packagename>
This guide gave an introduction on how to use the osc tool to checkout sources. The next page will cover building your project. Click here to open the 3rd part.