MeeGo wiki - User contributions [en]

How to development with multiple packages with dependencies

2011-07-07T14:14:32Z

Xiaoqiang0:

This page is for customers, who need to develop their own packages, including libraries and applications, which are not included in MeeGo official repo. In this seriono, the customers need create/maintain their own repo for their own packages, below script shows how to build multiple packages with dependcies, and how to create a repo to feed the MIC (MeeGo Image Creator).

<pre>
#!/bin/bash

# mkdir -p localbuild/{repo,src}
# put all src.rpm (or source code package with *.spec) in src/
# cd localbuild/

# NOTE:
# 1. pacakges sequence is IMPORTANT, check *.spec and put "BuildRequires" package in the front, for example:
# libplatform_config-20.0.3-1.4.src.rpm requires libhtuple-devel and kernel-headers-cetv to finish build.
# 2. This script suppose that you have an httpd server running. and http://localhost/MeeGo/repo/, which point
to LOCAL_REPO_DIR in system directory.

PACKAGES="
kernel-headers-cetv-20.0.1-1.2.src.rpm
libhtuple-20.0.1-1.2.src.rpm
libplatform_config-20.0.3-1.4.src.rpm
"

for package in $PACKAGES
do
echo "build package=[$package]"
sudo build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/
--repository http://localhost/local/repo/dir/ --arch i686 src/$package
echo "copy over..."
find /var/tmp/build-root/home/abuild/rpmbuild/ -name *.rpm -exec cp {} $LOCAL_REPO_DIR \;
createrepo $LOCAL_REPO_DIR
done
</pre>

"local/repo/dir/" can be then added to the *.ks file for MIC, something like "repo --name=local --baseurl=file:///path/to/local/repo/ --save"

How to development with multiple packages with dependencies

2011-07-07T14:13:51Z

Xiaoqiang0:

This page is for customers, who need to develop their own packages, including libraries and applications, which are not included in MeeGo official repo. In this seriono, the customers need create/maintain their own repo for their own packages, below script shows how to build multiple packages with dependcies, and how to create a repo to feed the MIC (MeeGo Image Creator).

<pre>
#!/bin/bash

# mkdir -p localbuild/{repo,src}
# put all src.rpm (or source code package with *.spec) in src/
# cd localbuild/

# NOTE:
# 1. pacakges sequence is IMPORTANT, check *.spec and put "BuildRequires" package in the front, for example:
# libplatform_config-20.0.3-1.4.src.rpm requires libhtuple-devel and kernel-headers-cetv to finish build.
# 2. This script suppose that you have an httpd server running. and http://localhost/MeeGo/repo/, which is LOCAL_REPO_DIR in system directory.

PACKAGES="
kernel-headers-cetv-20.0.1-1.2.src.rpm
libhtuple-20.0.1-1.2.src.rpm
libplatform_config-20.0.3-1.4.src.rpm
"

for package in $PACKAGES
do
echo "build package=[$package]"
sudo build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/
--repository http://localhost/local/repo/dir/ --arch i686 src/$package
echo "copy over..."
find /var/tmp/build-root/home/abuild/rpmbuild/ -name *.rpm -exec cp {} $LOCAL_REPO_DIR \;
createrepo $LOCAL_REPO_DIR
done
</pre>

"local/repo/dir/" can be then added to the *.ks file for MIC, something like "repo --name=local --baseurl=file:///path/to/local/repo/ --save"

How to development with multiple packages with dependencies

2011-07-07T14:12:20Z

Xiaoqiang0:

This page is for customers, who need to develop their own packages, including libraries and applications, which are not included in MeeGo official repo. In this seriono, the customers need create/maintain their own repo for their own packages, below script shows how to build multiple packages with dependcies, and how to create a repo to feed the MIC (MeeGo Image Creator).

<pre>
#!/bin/bash

# mkdir -p localbuild/{repo,src}
# put all src.rpm (or source code package with *.spec) in src/
# cd localbuild/

# NOTE:
# 1. pacakges sequence is IMPORTANT, check *.spec and put "BuildRequires" package in the front, for example:
# libplatform_config-20.0.3-1.4.src.rpm requires libhtuple-devel and kernel-headers-cetv to finish build.
# 2. This script suppose that you have an httpd server running. and http://localhost/MeeGo/repo/, which is LOCAL_REPO_DIR in system directory.

PACKAGES="
kernel-headers-cetv-20.0.1-1.2.src.rpm
libhtuple-20.0.1-1.2.src.rpm
libplatform_config-20.0.3-1.4.src.rpm
"

for package in $PACKAGES
do
echo "build package=[$package]"
sudo build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/
--repository http://localhost/local/repo/dir/ --arch i686 src/$package
echo "copy over..."
find /var/tmp/build-root/home/abuild/rpmbuild/ -name *.rpm -exec cp {} $LOCAL_REPO_DIR \;
createrepo $LOCAL_REPO_DIR
</pre>

"local/repo/dir/" can be then added to the *.ks file for MIC, something like "repo --name=local --baseurl=file:///path/to/local/repo/ --save"

How to development with multiple packages with dependencies

2011-07-04T09:57:45Z

Xiaoqiang0: Created page with "This page is for customs, who need to develop their own packages, including libraries and applications, which are not included in MeeGo official repo. In this seriono, the custom..."

This page is for customs, who need to develop their own packages, including libraries and applications, which are not included in MeeGo official repo. In this seriono, the customs need create / maintain their own repo for their own packages, as to the creation of repo, the follow link can help.

Distribution

2011-07-04T09:54:25Z

Xiaoqiang0: /* Development without MeeGo OBS account */

This page describes basic information you needed if you want to contribute to MeeGo. Target audience is community member who wish to involve in MeeGo development.

== Package Management and Development ==
=== Overview ===
Like other Linux distros, MeeGo is a package-based system, and it is using RPM package end. The RPM packages are managed in ZYpper repos. The MeeGo development is done by using [[Open Build System]] (OBS). If you are a serious and frequent MeeGo contributor, you need an OBS account to commit your changes back to MeeGo. Other casual contributors can work without using OBS, but you need a MeeGo development team member to help review and commit your changes into MeeGo.

The process of develop with an OBS account:
Branch, Check-out, Make changes, Deployment the new package and test, Make a new image (optional), Sumbmit your changes.

TODO: Tutorial?

The process of develop without using OBS:
Download MeeGo from a repo, build a chroot env, get the source of a package, make changes, build and test the new package, how to debug the local build, find a MeeGo team member to sponsor your changes and submit them back.

TODO: Tutorial?

* MeeGo is using RPM as package end and ZYpper for repo
** [[List of MeeGo releases and repos]]
* MeeGo is using Open Build System (OBS) for building: [[OBS basic]]
* [[Distribution/Package_Management|Package Management]]

=== Development with MeeGo OBS account ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|Request a new OBS account]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Link packages and adding a repository]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]

=== Development without MeeGo OBS account ===
* [[Local_Build_Without_OBS_Needed|Build and develop packages without OBS ]]
* [[Recompile_kernel | Example: Recompile kernel]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [[How to development with multiple packages with dependencies]]

=== Packaging ===
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Application Packaging Tutorial]]

=== Process ===
* [[Release_Engineering/New_Package_Checklist|Checklist for new package submissions]]
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

== Developer Tools ==
=== Image Creation ===
* [[Image_Creation|MIC2]]
* [[Image_Creation_For_Beginners|MIC2 for Beginners]]
* [[Image Configurations & KS files]]

=== OBS command line ===
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout & branch]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

=== Spec tool ===
* [[Spectacle|Spectacle]]

== Distribution Infrastructure ==
* [[Build_Infrastructure|Build Infrastructure - OBS]]
* [[Release Infrastructure - BOSS]]

== Software Repo ==
* [[Create and update repos]]

== Links ==
* [[Release_Engineering|Release Engineering]]
* [[Quality/Compliance|Compliance]]
* [[Quality|Quality]]

Distribution

2011-07-04T09:53:54Z

Xiaoqiang0: /* Development without MeeGo OBS account */

This page describes basic information you needed if you want to contribute to MeeGo. Target audience is community member who wish to involve in MeeGo development.

== Package Management and Development ==
=== Overview ===
Like other Linux distros, MeeGo is a package-based system, and it is using RPM package end. The RPM packages are managed in ZYpper repos. The MeeGo development is done by using [[Open Build System]] (OBS). If you are a serious and frequent MeeGo contributor, you need an OBS account to commit your changes back to MeeGo. Other casual contributors can work without using OBS, but you need a MeeGo development team member to help review and commit your changes into MeeGo.

The process of develop with an OBS account:
Branch, Check-out, Make changes, Deployment the new package and test, Make a new image (optional), Sumbmit your changes.

TODO: Tutorial?

The process of develop without using OBS:
Download MeeGo from a repo, build a chroot env, get the source of a package, make changes, build and test the new package, how to debug the local build, find a MeeGo team member to sponsor your changes and submit them back.

TODO: Tutorial?

* MeeGo is using RPM as package end and ZYpper for repo
** [[List of MeeGo releases and repos]]
* MeeGo is using Open Build System (OBS) for building: [[OBS basic]]
* [[Distribution/Package_Management|Package Management]]

=== Development with MeeGo OBS account ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|Request a new OBS account]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Link packages and adding a repository]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]

=== Development without MeeGo OBS account ===
* [[Local_Build_Without_OBS_Needed|Build and develop packages without OBS ]]
* [[Recompile_kernel | Example: Recompile kernel]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [How to development with multiple packages with dependencies]

=== Packaging ===
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Application Packaging Tutorial]]

=== Process ===
* [[Release_Engineering/New_Package_Checklist|Checklist for new package submissions]]
* [[Release_Engineering/Submission_Checklist|Developer's checklist for code submissions]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

== Developer Tools ==
=== Image Creation ===
* [[Image_Creation|MIC2]]
* [[Image_Creation_For_Beginners|MIC2 for Beginners]]
* [[Image Configurations & KS files]]

=== OBS command line ===
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout & branch]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

=== Spec tool ===
* [[Spectacle|Spectacle]]

== Distribution Infrastructure ==
* [[Build_Infrastructure|Build Infrastructure - OBS]]
* [[Release Infrastructure - BOSS]]

== Software Repo ==
* [[Create and update repos]]

== Links ==
* [[Release_Engineering|Release Engineering]]
* [[Quality/Compliance|Compliance]]
* [[Quality|Quality]]

Local Build Without OBS Needed

2011-07-04T09:04:27Z

Xiaoqiang0: /* Building your package using build */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages

You can get its public key for http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/noarch/meego-release-1.2.0-2.1.noarch.rpm

<pre>
$ wget http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/noarch/meego-release-1.2.0-2.1.noarch.rpm
$ rpm2cpio meego-release-1.2.0-2.1.noarch.rpm | cpio -idmv
$ rpm --import ./etc/pki/rpm-gpg/RPM-GPG-KEY-meego02
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 cpio-2.11-2.meego.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm

== Development your package using build ==

If you want to modify packages, such as add/modify/remove patches, you need unpack src.rpm first. Then development can be based on source code.

This command would unpack src.rpm to current directory, and your work can be in this directory.

rpm2cpio XXX.src.rpm | cpio -idmv

#If you want to add a patch, you just need copy the patch to current directory and add this patch in spec file.
#If you wan to remove patches, you just need to remove them in spec file.
#If you want to modify exist patch, you can modify the special patch and spec file need not to modify.

Once you development work is done, you can use ‘build’ command to generate new RPM based on you changes. Command as follows:

build --repository http://YYY/repos/oss/ia32/packages/ --arch i686 XXX.spec

binary RPM package can be found in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.

== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

On Debian, you should install 'qemu-user-static' from Squeeze (Debian 6.0) and later.

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.
If problem persist, see [https://bugs.meego.com/show_bug.cgi?id=18905 bug 18905]

== Another language version of this page ==

* [[不需要obs的本地build-_简体中文]]

Distribution

2011-07-04T08:33:22Z

Xiaoqiang0: /* Development with MeeGo OBS account */

This page describes basic information you needed if you want to contribute to MeeGo. Target audience is community member who wish to involve in MeeGo development.

== Package Management and Development ==
=== Overview ===
Like other Linux distros, MeeGo is a package-based system, and it is using RPM package end. The RPM packages are managed in ZYpper repos. The MeeGo development is done by using [[Open Build System]] (OBS). If you are a serious and frequent MeeGo contributor, you need an OBS account to commit your changes back to MeeGo. Other casual contributors can work without using OBS, but you need a MeeGo development team member to help review and commit your changes into MeeGo.

The process of develop with an OBS account:
Branch, Check-out, Make changes, Deployment the new package and test, Make a new image (optional), Sumbmit your changes.

The process of develop without using OBS:
Download MeeGo from a repo, build a chroot env, get the source of a package, make changes, build and test the new package, how to debug the local build, find a MeeGo team member to sponsor your changes and submit them back.

* MeeGo is using RPM as package end and ZYpper for repo
** [[List of MeeGo releases and repos]]
* MeeGo is using Open Build System (OBS) for building: [[OBS basic]]
* [[Distribution/Package_Management|Package Management]]

=== Development with MeeGo OBS account ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|Request a new OBS account]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Link packages and adding a repository]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]

=== Development without MeeGo OBS account ===
* [[Local_Build_Without_OBS_Needed|Build and develop packages without OBS ]]
* [[Recompile_kernel | Example: Recompile kernel]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]

=== Packaging ===
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Application Packaging Tutorial]]

=== Process ===
* [[Create new package in OBS]]
* [[Remove package from OBS]]
* [[Commit changes to OBS]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

== Developer Tools ==
=== Image Creation ===
* [[Image_Creation|MIC2]]
* [[Image_Creation_For_Beginners|MIC2 for Beginners]]
* [[Image Configurations & KS files]]

=== OBS command line ===
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout & branch]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

=== Spec tool ===
* [[Spectacle|Spectacle]]

== Distribution Infrastructure ==
* [[Build_Infrastructure|Build Infrastructure - OBS]]
* [[Release Infrastructure - BOSS]]

== Software Repo ==
* [[Create and update repos]]

== Links ==
* [[Release_Engineering|Release Engineering]]
* [[Quality/Compliance|Compliance]]
* [[Quality|Quality]]

Distribution/Package Management

2011-07-04T07:01:23Z

Xiaoqiang0: /* Querying */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n meego-app-photos
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in meego-handset*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in meego-ux-* # install all meego-ux modules
zypper in -t pattern meego-base # install meego-base pattern (packages needed for MeeGo base system)
zypper in vim -gedit # install vim and remove gedit in one go
zypper in vim oss:vim-commom # install vim-commpn from oss and vim from any repo
zypper in libzypp-9.1.2-9.1.i586.rpm # install libzypp rpm from local directory
zypper in -f PackageKit # force reinstallation of PackageKit

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words editor # look for 'editor' acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r oss # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern meego-base # show info about meego-base pattern
zypper info -t product openSUSE-FTP # show info about specified product

=== Update Management ===
There are two approaches to keeping your system up to date. One is patch-wise, the second is package-wise.

The patch-wise approach is particularly useful for people using stable releases and want update their systems with patches released through online update repositories. Update repositories are added by default during installation or upgrade of the system. [http://repo.meego.com/MeeGo/updates/ Here is the list of available official MeeGo update repositories].

The second, package-wise update is described in section Package Updates and servers for general updating of packages from any repository with their newer versions.

==== Listing Availabe Patches/Updates ====
You can get a list of available updates with:
zypper lu
To list all needed patch updates, do:
zypper lp
To list all the paches, including installed and available patches, the following command can help:
zypper patches

==== Applying Patches ====
To install / apply the needed patches, do:
zypper patch
==== Package Updates ====
To simply update installed packages with their newer available versions, do:
zypper up
Or just update one package with:
zyper update pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-04T06:59:09Z

Xiaoqiang0: /* Installing Packages */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n meego-app-photos
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in meego-handset*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in meego-ux-* # install all meego-ux modules
zypper in -t pattern meego-base # install meego-base pattern (packages needed for MeeGo base system)
zypper in vim -gedit # install vim and remove gedit in one go
zypper in vim oss:vim-commom # install vim-commpn from oss and vim from any repo
zypper in libzypp-9.1.2-9.1.i586.rpm # install libzypp rpm from local directory
zypper in -f PackageKit # force reinstallation of PackageKit

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

=== Update Management ===
There are two approaches to keeping your system up to date. One is patch-wise, the second is package-wise.

The patch-wise approach is particularly useful for people using stable releases and want update their systems with patches released through online update repositories. Update repositories are added by default during installation or upgrade of the system. [http://repo.meego.com/MeeGo/updates/ Here is the list of available official MeeGo update repositories].

The second, package-wise update is described in section Package Updates and servers for general updating of packages from any repository with their newer versions.

==== Listing Availabe Patches/Updates ====
You can get a list of available updates with:
zypper lu
To list all needed patch updates, do:
zypper lp
To list all the paches, including installed and available patches, the following command can help:
zypper patches

==== Applying Patches ====
To install / apply the needed patches, do:
zypper patch
==== Package Updates ====
To simply update installed packages with their newer available versions, do:
zypper up
Or just update one package with:
zyper update pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-04T06:53:59Z

Xiaoqiang0: /* How to select packages */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n meego-app-photos
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in meego-handset*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in yast* # install all yast modules
zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server)
zypper in vim -emacs # install vim and remove emacs in one go
zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo
zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory
zypper in -f subversion # force reinstallation of subversion

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

=== Update Management ===
There are two approaches to keeping your system up to date. One is patch-wise, the second is package-wise.

The patch-wise approach is particularly useful for people using stable releases and want update their systems with patches released through online update repositories. Update repositories are added by default during installation or upgrade of the system. [http://repo.meego.com/MeeGo/updates/ Here is the list of available official MeeGo update repositories].

The second, package-wise update is described in section Package Updates and servers for general updating of packages from any repository with their newer versions.

==== Listing Availabe Patches/Updates ====
You can get a list of available updates with:
zypper lu
To list all needed patch updates, do:
zypper lp
To list all the paches, including installed and available patches, the following command can help:
zypper patches

==== Applying Patches ====
To install / apply the needed patches, do:
zypper patch
==== Package Updates ====
To simply update installed packages with their newer available versions, do:
zypper up
Or just update one package with:
zyper update pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-03T07:49:20Z

Xiaoqiang0: /* Update Management */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in yast* # install all yast modules
zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server)
zypper in vim -emacs # install vim and remove emacs in one go
zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo
zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory
zypper in -f subversion # force reinstallation of subversion

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

=== Update Management ===
There are two approaches to keeping your system up to date. One is patch-wise, the second is package-wise.

The patch-wise approach is particularly useful for people using stable releases and want update their systems with patches released through online update repositories. Update repositories are added by default during installation or upgrade of the system. [http://repo.meego.com/MeeGo/updates/ Here is the list of available official MeeGo update repositories].

The second, package-wise update is described in section Package Updates and servers for general updating of packages from any repository with their newer versions.

==== Listing Availabe Patches/Updates ====
You can get a list of available updates with:
zypper lu
To list all needed patch updates, do:
zypper lp
To list all the paches, including installed and available patches, the following command can help:
zypper patches

==== Applying Patches ====
To install / apply the needed patches, do:
zypper patch
==== Package Updates ====
To simply update installed packages with their newer available versions, do:
zypper up
Or just update one package with:
zyper update pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-03T07:45:19Z

Xiaoqiang0: /* Listing Availabe Patches/Updates */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in yast* # install all yast modules
zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server)
zypper in vim -emacs # install vim and remove emacs in one go
zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo
zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory
zypper in -f subversion # force reinstallation of subversion

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

=== Update Management ===
There are two approaches to keeping your system up to date. One is patch-wise, the second is package-wise.

The patch-wise approach is particularly useful for people using stable releases and want update their systems with patches released through online update repositories. Update repositories are added by default during installation or upgrade of the system. [http://repo.meego.com/MeeGo/updates/ Here is the list of available official MeeGo update repositories].

The second, package-wise update is described in section Package Updates and servers for general updating of packages from any repository with their newer versions.

==== Listing Availabe Patches/Updates ====
You can get a list of available updates with:
zypper lu
To list all needed patch updates, do:
zypper lp
To list all the paches, including installed and available patches, the following command can help:
zypper patches

==== Applying Patches ====
To install / apply the needed patches, do:
zypper patch

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-03T07:39:55Z

Xiaoqiang0: /* zypper */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in yast* # install all yast modules
zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server)
zypper in vim -emacs # install vim and remove emacs in one go
zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo
zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory
zypper in -f subversion # force reinstallation of subversion

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

=== Update Management ===
There are two approaches to keeping your system up to date. One is patch-wise, the second is package-wise.

The patch-wise approach is particularly useful for people using stable releases and want update their systems with patches released through online update repositories. Update repositories are added by default during installation or upgrade of the system. [http://repo.meego.com/MeeGo/updates/ Here is the list of available official MeeGo update repositories].

The second, package-wise update is described in section Package Updates and servers for general updating of packages from any repository with their newer versions.

==== Listing Availabe Patches/Updates ====

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-03T07:33:18Z

Xiaoqiang0: /* Package Management */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in yast* # install all yast modules
zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server)
zypper in vim -emacs # install vim and remove emacs in one go
zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo
zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory
zypper in -f subversion # force reinstallation of subversion

====Removing Packages====
The remove command is very much like the install command, except that the effect is the opposite
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-03T07:25:36Z

Xiaoqiang0: /* Installing Packages */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
You can install packages by name...
zypper install

...or by capability they provide:
# zypper in MozillaFirefox \< 3

Other install examples as follows:

zypper in yast* # install all yast modules
zypper in -t pattern lamp_server # install lamp_server pattern (packages needed for a LAMP server)
zypper in vim -emacs # install vim and remove emacs in one go
zypper in amarok packman:libxine1 # install libxine1 from packman and amarok from any repo
zypper in bitchx-1.1-81.x86_64.rpm # install bitchx rpm from local directory
zypper in -f subversion # force reinstallation of subversion

====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-03T07:17:51Z

Xiaoqiang0: /* package && pattern && patch */

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - Software package, which is a type of file format where software programs and installation material is grouped together. Patches and patternsare also commonly referred to as different types of packages.

'''Patch''' - Represents a package or a group of packages needed to install an update (a bug fix mostly).

'''patterns''' - Represents a group of packages. Just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T01:48:24Z

Xiaoqiang0:

All software on MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc
=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution

2011-07-02T00:55:39Z

Xiaoqiang0: /* OBS & repos */

== Development ==
=== OBS & Repos & Package===
* [[OBS basic]]
* [[repos and released images]]
* [[Create and update repos]]
* [[Distribution/Package_Management|Package Management]]

=== Development with MeeGo OBS account ===
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_webinterface|How to use the web interface to view, manage and build your packages.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]

=== Development without MeeGo OBS account ===
* [[Local_Build_Without_OBS_Needed|Build and develop packages without OBS ]]
* [[Recompile_kernel | Example: Recompile kernel]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]

=== Packaging ===
* [[Build_Infrastructure/Packagers_Developers#MeeGo_Packaging_guidelines_and_Howto|MeeGo Packaging guidelines and howto]]

=== Process ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|Request a new OBS account]]
* [[Create new package in OBS]]
* [[Remove package from OBS]]
* [[Commit changes to OBS]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

== Developer Tools ==
=== Image Creation ===
* [[Image_Creation|MIC2]]
* [[Image_Creation_For_Beginners|MIC2 for Beginners]]
* [[Image Configurations & KS files]]

=== OBS command line ===
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout & branch]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

=== Spec tool ===
* [[Spectacle|Spectacle]]

== Distribution Infrastructure ==
* [[Build_Infrastructure|Build Infrastructure - OBS]]
* [[Release Infrastructure - BOSS]]

== Links ==
* [[Release_Engineering|Release Engineering]]
* [[Quality/Compliance|Compliance]]
* [[Quality|Quality]]

Distribution/Package Management

2011-07-02T00:41:04Z

Xiaoqiang0: /* How to select packages */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc
=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in *meegotouch*
* by specifying an .rpm package file to install

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:40:14Z

Xiaoqiang0: /* How to select packages */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc
=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in gnome-packagekit
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in oss:zypper
*by package name using wildcards
zypper in yast*ftp*
* by specifying an .rpm package file to install

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:38:26Z

Xiaoqiang0: /* Package Management */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc
=== Repository Management ===

=== Package Management ===
====How to select packages====
There are several ways in which you can choose packages for installation or removal.

*by capability name
zypper in eclipse
zypper in qt
*by capability name and/or architecture and/or version
zypper in 'zypper<0.12.10'
zypper in zypper.i586=0.12.11
*by exact package name (--name)
zypper in -n ftp
*by exact package name and repository (implies --name)
zypper in factory:zypper
*by package name using wildcards
zypper in yast*ftp*
* by specifying an .rpm package file to install

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:32:00Z

Xiaoqiang0: /* Display Package Information */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc
=== Repository Management ===

=== Package Management ===

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit #displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:31:30Z

Xiaoqiang0: /* zypper */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc
=== Repository Management ===

=== Package Management ===

====Installing Packages====
zypper install pkgname
====Removing Packages====
zypper remove pkgname

=== Querying ===

==== Search Packages====
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

====Display Package Information====
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:28:09Z

Xiaoqiang0: /* Display Package Information */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Search Packages===
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

===List Packages===
zypper search
===Display Package Information===
In order to obtaining information about packages, the following command can be used:
zypper info PackageKit displays detailed information about package named 'PackageKit'
zypper info -t patch MozillaFirefox # show information about 'MozillaFirefox' patch
zypper patch-info MozillaFirefox # the same as above
zypper info -t pattern lamp_server # show info about 'lamp_server' pattern
zypper info -t product openSUSE-FTP # show info about specified product

===Installing Packages===
zypper install pkgname
===Removing Packages===
zypper remove pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:26:39Z

Xiaoqiang0: /* Search Packages */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Search Packages===
zypper search --help
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

===List Packages===
zypper search
===Display Package Information===
In order to obtaining information about packages, the following command can be used:
zypper info pkgname

===Installing Packages===
zypper install pkgname
===Removing Packages===
zypper remove pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:26:24Z

Xiaoqiang0: /* Display Package Information */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Search Packages===
zypper search --help
===List Packages===
zypper search
===Display Package Information===
In order to obtaining information about packages, the following command can be used:
zypper info pkgname

===Installing Packages===
zypper install pkgname
===Removing Packages===
zypper remove pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:25:03Z

Xiaoqiang0: /* Display Package Information */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

==Package Management Architecture==

[[File: Package_Management_Architecture.png|750x600px]]

The whole stack has RPM at the lowest level.RPM is type of package management system. On top of RPM is Zypp software management library for RPM-based systems. It's also know by it‘s package name, libzypp.

on top of libzypp, there are various user interfaces or Package Management UI, like Zypper and YaST, the PackageKit Zypp backend, which enables the use of any PackageKit application.

==zypper==
===package && pattern && patch ===
'''Package''' - a type of file format where software programs and installation material is grouped together

'''Update & Patch''' - Update is a single replacement (newer version of a) package, but Patch is information about one or multi packages updates.

'''patterns''' - just like the group concept in yum repo. It’s a group of packages belong to one type. Such as Graphics, development, etc

=== Search Packages===
zypper search --help
===List Packages===
zypper search
===Display Package Information===
In order to obtaining information about packages, the following command can be used:
zypper info pkgname
zypper se -dC --match-words RSI # look for RSI acronym (case-sensitively), also in summaries and descriptions
zypper se 'yast*' # show all packages starting with 'yast' (beware of shell expansion, quote the strings if unsure!)
zypper se -r packman # list all packages from 'packman' repository
zypper se -i sqlite # show all installed packages containing 'sqlite' in their name
zypper se -t pattern -r repo-oss # list all patterns available in the 'repo-oss' repository
zypper se -t product # list all available products

===Installing Packages===
zypper install pkgname
===Removing Packages===
zypper remove pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-02T00:13:22Z

Xiaoqiang0: /* package && pattern && patch */

Distribution/Package Management

2011-07-02T00:13:05Z

Xiaoqiang0: /* package && pattern && patch */

Distribution/Package Management

2011-07-02T00:02:28Z

Xiaoqiang0: /* package && pattern && patch */

Distribution/Package Management

2011-07-01T23:58:08Z

Xiaoqiang0: /* Package Management Architecture */

Distribution/Package Management

2011-07-01T23:56:28Z

Xiaoqiang0: /* Package Management Architecture */

Distribution/Package Management

2011-07-01T23:54:39Z

Xiaoqiang0: /* Package Management Architecture */

Distribution/Package Management

2011-07-01T23:54:10Z

Xiaoqiang0: /* Package Management Architecture */

Distribution/Package Management

2011-07-01T23:52:21Z

Xiaoqiang0:

Distribution/Package Management

2011-07-01T15:52:00Z

Xiaoqiang0: /* PackageKit */

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.
==zypper==
===package && pattern && patch ===
=== Search Packages===
zypper search --help
===List Packages===
zypper search
===Display Package Information===
zypper
===Installing Packages===
zypper install pkgname
===Removing Packages===
zypper remove pkgname

==PackageKit==

=== Update Packages with Gnome PackageKit ===
Gnome PackageKit can be available on NetBook and IVI.
==== Updating Packages with Software Update =====
In the Software Updates window, all available updates are listed along with the names of the packages being updated (minus the .rpm suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
==== Using Add/Remove Software =====
PackageKit's Software Update GUI window is a separate application from its Add/Remove Software application, although the two have intuitively similar interfaces.

=== Manage packages with PackageKit command line tool ===

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Distribution/Package Management

2011-07-01T15:43:45Z

Xiaoqiang0:

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.
==zypper==
===package && pattern && patch ===
=== Search Packages===
zypper search --help
===List Packages===
zypper search
===Display Package Information===
zypper
===Installing Packages===
zypper install pkgname
===Removing Packages===
zypper remove pkgname

==PackageKit==

== How to report a bug ==
=== PackageKit or Package Manager UI bug ===
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
For PackageKit or Package Manager UI issue
Steps to get logs:
* Setup system Environment
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
* start packagekitd manually. In one terminal execute:
#killall -9 packagekitd
#/usr/libexec/packagekitd -v >packagekitd.log
* In another terminal execute your script/command to reproduce bug.
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.
=== zypper command bug ===
For Zypper issue while you using zypper command, using the following steps to get logs:
* Setup system Environment
#rm /var/log/zypper.log -f
* set log level and reproduce bug using zypper
#export ZYPP_LIBSAT_FULLLOG=1
#zypper xxx yyy
or using the following log level
#export ZYPP_FULLLOG=1
#zypper xxx yyy
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Package Management

2011-07-01T15:27:29Z

Xiaoqiang0:

==A==
sdasdf
=== A1 ===
== B ==

Package Management

2011-07-01T15:26:57Z

Xiaoqiang0: Created page with "==A== sdasdf === A1 === == B =="

==A==
sdasdf
=== A1 ===
== B ==

Distribution

2011-07-01T15:23:56Z

Xiaoqiang0: /* OBS & repos */

== Development ==
=== OBS & repos ===
* [[OBS basic]]
* [[repos and released images]]
* [[Create and update repos]]
* [[Distribution/Package_Management|Package Management]]

=== Development with MeeGo OBS account ===
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_webinterface|How to use the web interface to view, manage and build your packages.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]

=== Development without MeeGo OBS account ===
* [[Local_Build_Without_OBS_Needed|Build and develop packages without OBS ]]
* [[Recompile_kernel | Example: Recompile kernel]]
* [[Distribution/Create_image_based_on_new_RPM|Create image based on new RPM]]

=== Packaging ===
* [[Build_Infrastructure/Packagers_Developers#MeeGo_Packaging_guidelines_and_Howto|MeeGo Packaging guidelines and howto]]

=== Process ===
* [[Build_Infrastructure/Packagers_Developers#How_to_get_started|Request a new OBS account]]
* [[Create new package in OBS]]
* [[Remove package from OBS]]
* [[Commit changes to OBS]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

== Developer Tools ==
=== Image Creation ===
* [[Image_Creation|MIC2]]
* [[Image_Creation_For_Beginners|MIC2 for Beginners]]
* [[Image Configurations & KS files]]

=== OBS command line ===
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout & branch]]
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

=== Spec tool ===
* [[Spectacle|Spectacle]]

== Distribution Infrastructure ==
* [[Build_Infrastructure|Build Infrastructure - OBS]]
* [[Release Infrastructure - BOSS]]

== Links ==
* [[Release_Engineering|Release Engineering]]
* [[Quality/Compliance|Compliance]]
* [[Quality|Quality]]

Create and update repos

2011-07-01T10:37:26Z

Xiaoqiang0: /* Local Repository in MeeGo */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===
1. Create the directory structure of the repository
mkdir /var/www/html/meego/
mkdir /var/www/html/meego/i586
mkdir /var/www/html/meego/i686
mkdir /var/www/html/meego/noarch
2. Copy the RPMs to correct directory
3. Create repository metadata
createrepo /var/www/html/meego/

This might take some time, depending upon the speed of your processor(s) and HD. On successful conclusion, createrepo should create a directory /repodata. The contents should be:

filelists.xml.gz, other.xml.gz, primary.xml.gz, repomd.xml

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata | Updateinfo]

More infomation can be got from [http://moblin.intel.com/wiki/MeeGo_1.0_Update_Process |Update Process ]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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.

The following commands can help you to add local repo to system:
#zypper addrepo -t plaindir file:///root/repo/ local
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:33:19Z

Xiaoqiang0: /* Update repository creation */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===
1. Create the directory structure of the repository
mkdir /var/www/html/meego/
mkdir /var/www/html/meego/i586
mkdir /var/www/html/meego/i686
mkdir /var/www/html/meego/noarch
2. Copy the RPMs to correct directory
3. Create repository metadata
createrepo /var/www/html/meego/

This might take some time, depending upon the speed of your processor(s) and HD. On successful conclusion, createrepo should create a directory /repodata. The contents should be:

filelists.xml.gz, other.xml.gz, primary.xml.gz, repomd.xml

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata | Updateinfo]

More infomation can be got from [http://moblin.intel.com/wiki/MeeGo_1.0_Update_Process |Update Process ]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:32:58Z

Xiaoqiang0: /* Update repository creation */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===
1. Create the directory structure of the repository
mkdir /var/www/html/meego/
mkdir /var/www/html/meego/i586
mkdir /var/www/html/meego/i686
mkdir /var/www/html/meego/noarch
2. Copy the RPMs to correct directory
3. Create repository metadata
createrepo /var/www/html/meego/

This might take some time, depending upon the speed of your processor(s) and HD. On successful conclusion, createrepo should create a directory /repodata. The contents should be:

filelists.xml.gz, other.xml.gz, primary.xml.gz, repomd.xml

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [[http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata | Updateinfo]]

More infomation can be got from [http://moblin.intel.com/wiki/MeeGo_1.0_Update_Process |Update Process ]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:32:23Z

Xiaoqiang0: /* Update repository creation */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===
1. Create the directory structure of the repository
mkdir /var/www/html/meego/
mkdir /var/www/html/meego/i586
mkdir /var/www/html/meego/i686
mkdir /var/www/html/meego/noarch
2. Copy the RPMs to correct directory
3. Create repository metadata
createrepo /var/www/html/meego/

This might take some time, depending upon the speed of your processor(s) and HD. On successful conclusion, createrepo should create a directory /repodata. The contents should be:

filelists.xml.gz, other.xml.gz, primary.xml.gz, repomd.xml

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [[http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata | Updateinfo]]

More infomation can be got from [[http://moblin.intel.com/wiki/MeeGo_1.0_Update_Process|Update Process ]]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:30:14Z

Xiaoqiang0: /* Create a repo */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===
1. Create the directory structure of the repository
mkdir /var/www/html/meego/
mkdir /var/www/html/meego/i586
mkdir /var/www/html/meego/i686
mkdir /var/www/html/meego/noarch
2. Copy the RPMs to correct directory
3. Create repository metadata
createrepo /var/www/html/meego/

This might take some time, depending upon the speed of your processor(s) and HD. On successful conclusion, createrepo should create a directory /repodata. The contents should be:

filelists.xml.gz, other.xml.gz, primary.xml.gz, repomd.xml

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [[http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata | Updateinfo]]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:21:39Z

Xiaoqiang0: /* Update repository creation */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [[http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata | Updateinfo]]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:20:57Z

Xiaoqiang0: /* Update repository creation */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [[http://repo.meego.com/MeeGo/updates/1.1/core/| Updateinfo]]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:20:09Z

Xiaoqiang0: /* Update repository creation */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from [[http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/repodata/41a49610180ccd7902a6e9e9f2fa1ec56e8de07f2e81cc6fec0aa562d21b11a1-updateinfo.xml.gz|Updateinfo.xml]]

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:16:21Z

Xiaoqiang0: /* zypper */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions

You can get more information from 'zypper update --help'. For example, you can use -t option to specify a patch or package.

Create and update repos

2011-07-01T10:14:25Z

Xiaoqiang0: /* How to use local repo in MeeGo = */

This page describes the basic steps to create and update a Zypper repo that can be used with MeeGo systems.

== Why and when should I create a new repo? ==

== Requirements ==
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.

== Create a repo ==

=== General repository creation ===

=== Update repository creation ===
You need to write additional updateinfo for your updaterepo. Example can be got from

== Add a repo to MeeGo ==
Package Management subsystem responsible for repo management.

=== Add repo from remote repo file===
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 base url ===
If the repo file does 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 -t rpm-md http://download.meego.com/live/Trunk/standard/ Trunk
#cat /etc/zypp/repos.d/Trunk.repo
[Trunk]
name=Trunk
enabled=1
autorefresh=0
baseurl=http://download.meego.com/live/Trunk/standard
type=rpm-md
keeppackages=0
#zypper addrepo --help //More infomation about adding 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
#cat /etc/zypp/repos.d/local.repo
[local]
name=local
enabled=1
autorefresh=0
baseurl=file:///root/repo/
type=plaindir
keeppackages=0
If you want to list the package in your local repo, the follow command can helo you.
#zypper search --repo local

== Use Repo to update your system ==

Once your repo is installed correctly in MeeGo, next work would be update packages from repo. There're several way you can follow.

===Package Manager UI (gnome-packagekit, ect.)===
If your repo is official update repo, you can use this method to update patches, but for package update, you'd better use command line tool, such as pkcon or zypper.
=== PackageKit command line toole (pkcon)===

pkcon get-updates # list the avaliable updates
pkcon update [package name or patch name]
=== zypper ===
zypper list-patches, lp # List needed patches.
zypper list-updates, lu # List available updates.
zypper update, up # Update installed packages with newer versions