(Added "requirement" section.) |
Xiaoqiang0 (Talk | contribs) |
||
| Line 7: | Line 7: | ||
== Create a repo == | == Create a repo == | ||
| + | == Add a repo to MeeGo == | ||
| + | Package Management subsystem responsible for repo management. | ||
| + | |||
| + | === Add repo from remote http / ftp server === | ||
| + | OBS always create a repo for each OBS project, for example project 'Trunk' have a repo http://download.meego.com/live/Trunk/standard/. and there's also a repo file named Trunk.repo. zypper can help to add the repo to meego system, commands as follows: | ||
| + | |||
| + | zypper addrepo http://download.meego.com/live/Trunk/standard/Trunk.repo | ||
| + | |||
| + | === Add repo from remote http / ftp url === | ||
| + | If the repo file is not exist, and we just know the repo base url (eg: http://download.meego.com/live/Trunk/standard/), pkcon command can help to add this repo, commands as follows: | ||
| + | |||
| + | zypper addrepo http://download.meego.com/live/Trunk/standard/ | ||
== Add new packages to an old repo == | == Add new packages to an old repo == | ||
| + | |||
| + | == Local Repository in MeeGo == | ||
| + | Local repo is useful, and it does not depend on http server, and can be used to update/install packages with complicate dependency. | ||
| + | ==== How to Create a local repo === | ||
| + | You need to install createrepo first, and then prepare the RPMs you want to put them to repo: | ||
| + | |||
| + | cp XX/YY/*.rpm . | ||
| + | createrepo . | ||
| + | |||
| + | === How to use local repo in MeeGo ==== | ||
| + | |||
| + | zypper addrepo -t plaindir file:///root/repo/ local | ||
This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.
Contents |
A useful repo should reside on a web server that your MeeGo client machines can access. The only requirement on the host server is that it runs an HTTP service and can share a directory. Either Linux or Windows IIS are fine. If you are using Windows as a web server, you do need another Linux machine to create and maintain the repo.
Package Management subsystem responsible for repo management.
OBS always create a repo for each OBS project, for example project 'Trunk' have a repo http://download.meego.com/live/Trunk/standard/. and there's also a repo file named Trunk.repo. zypper can help to add the repo to meego system, commands as follows:
zypper addrepo http://download.meego.com/live/Trunk/standard/Trunk.repo
If the repo file is not exist, and we just know the repo base url (eg: http://download.meego.com/live/Trunk/standard/), pkcon command can help to add this repo, commands as follows:
zypper addrepo http://download.meego.com/live/Trunk/standard/
Local repo is useful, and it does not depend on http server, and can be used to update/install packages with complicate dependency.
You need to install createrepo first, and then prepare the RPMs you want to put them to repo:
cp XX/YY/*.rpm . createrepo .
zypper addrepo -t plaindir file:///root/repo/ local