MeeGo wiki - User contributions [en]

QtInternationalization

2011-06-14T18:37:05Z

Pmccarty: Minor reorg... I clearly did not read ahead to the next section ;)

=Internationalization=

This is a developer's guide to internationalization (i18n) within the MeeGo UX project.

==Localizable Strings==

The most basic step in internationalization is to identify any user-visible strings in your application and replace them with code that looks up the appropriate string for the current locale. The way this is accomplished in Qt C++ code is to simply wrap the string with <code>tr()</code>:

<pre>QString label = tr("Ring tone:");</pre>

This is accomplished in Qt Quick (QML) code by wrapping the string with qsTr():

<pre>Text {
id: dialogTitle
text: qsTr("Find contacts")
...</pre>

There is a Qt command-line tool ''lupdate'' that scans source code for these <code>tr()</code> and <code>qsTr()</code> macros and pulls out the identified strings. It writes them into a ".ts file," an XML-format file that lists information about where the strings were found. In UX projects, we generate these TS files automatically when creating the dist tarball that we push to OBS.

Your top-level .pro file should have lines like these:

<pre>TRANSLATIONS += .qml lib/.h lib/*.cpp
PROJECT_NAME = meego-app-example

dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += git clone . $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION}/.git &&
dist.commands += rm -f $${PROJECT_NAME}-$${VERSION}/.gitignore &&
dist.commands += mkdir -p $${PROJECT_NAME}-$${VERSION}/ts &&
dist.commands += lupdate $${TRANSLATIONS} -ts $${PROJECT_NAME}-$${VERSION}/ts/$${PROJECT_NAME}.ts &&
dist.commands += tar jcpvf $${PROJECT_NAME}-$${VERSION}.tar.bz2 $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += echo; echo Created $${PROJECT_NAME}-$${VERSION}.tar.bz2</pre>

Make sure that <code>TRANSLATIONS</code> is set to include all files with translatable strings (you may need to include other subdirectories and .js files, for instance). Make sure that <code>PROJECT_NAME</code> is set to your application name.

Whenever you check in an update to OBS, you should create a clean tarball from git source. To create this tarball, run the following commands from the toplevel directory in your git tree:

<pre>$ qmake
$ make dist
</pre>

Then copy the generated tarball up to OBS. Bump the version up once a week. You should never submit an "sr" for the same version twice. But you can push to OBS multiple times throughout the week without doing an "sr."

Later these TS files are translated into various languages, and each one is compiled into a .qm binary file that allows efficient string lookup at runtime. Elsewhere you need to load a translator for each .qm file in your app, but this is handled automatically by our meego-qml-launcher for QML applications, so you generally don't have to think about. You just name your .ts file with your package name and it will be handled correctly.

==String Concatentation==

A common pitfall for i18n is building up strings by concatenation. You do this using assumptions about grammar and order that are true for your own language, but may not be true for another language. For example, consider this code:

<pre>function getBestPepperColor() {
return qsTr("red")
}

var message = qsTr("Tabasco is made from peppers selected using a ") + getBestPepperColor() + qsTr(" stick")</pre>

But in French, "red stick" is "bâton rouge". If you use concatenation as above, it will come out as "rouge bâton" in translation... incorrect!

So here's the solution:

<pre>var message = qsTr("Tabasco is made from peppers selected using a %1 stick").arg(getBestPepperColor())</pre>

Now the French translator will come up with something like:
<source>Tabasco est faite à partir de piments sélectionnés à l'aide d'un bâton %1.</source>
They are able to move the <code>%1</code> around to the right place for their language.

Another example is where there are multiple variables in the string. The order of the variables may need to change in translation. This cannot happen if you're concatenating.

Wrong:

<pre>// dateHeader will be e.g. "March 14th"
var dateHeader = getLocalizedMonth() + " " + getLocalizedDay()</pre>

This looks right because the month and day are localized, but in another language maybe the day needs to come first, like "14. Марта" in Russian.

Right:

<pre>// localized date header: %1 is month, %2 is day of month
var dateHeader = qsTr("%1 %2").arg(getLocalizedMonth()).arg(getLocalizedDay())</pre>

'''Note:''' There is a problem with the tools in QML in that the translator will only see "%1 %2" so they won't know what to do with it. In Qt, you can pass a second argument to tr() to give the translator a hint, for example:

<pre>QString dateFormat(tr("%1 %2", "%1 is the month, %2 is the day of the month"));
QString dateHeader = dateFormat.arg(getLocalizedMonth(), getLocalizedDay());</pre>

Also notice that the "<code>arg()</code>" function on QString can take multiple arguments, unlike in QML (to my knowledge).

==Translator comments==

Strings like "%1 %2" cannot get correctly translated by translators without knowing some context. It is possible to add a comment intended for translators to help them.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#translator-comments for more information.

In QML, a translator comment must be added to the line immediately preceding the affected string. For example:

<pre>//: This is a date range (start date - end date)
string: qsTr("%1 - %2")
</pre>

For more information on this topic, see http://lists.meego.com/pipermail/meego-il10n/2011-June/000516.html

==Disambiguation of strings ==

Imagine an application that uses the translatable string "Read" in one place as an action (e.g. a button that enables the user to read something), and in another place uses the translatable string "Read" to mark an element that has been read. The two different meanings (and translations to other languages) require disambiguation as otherwise they will end up as the same string in the translation files and can only receive exactly one translation that will be wrong in 50% of the cases.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#disambiguation for more information how to solve this.

An example for QML:

<pre>//: %1 is the number of transactions
text: qsTr("Total volume is %1", "transactions").arg(num)

//: %1 is the volume of water
text: qsTr("Total volume is %1", "watervolume").arg(vol)
</pre>

==Plural handling==

Many languages have more than one plural form (e.g. Czech has one plural form for 2-4 and another one for >=5) or complex rules (e.g. Arabic uses the singular form for amounts of 1, 11, 21, 31, ...), hence code like
<pre>n == 1 ? tr("%n message saved") : tr("%n messages saved")</pre>
will fail for these languages.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#handling-plurals for more information how to solve this.

==Supported locales==

The locales which must be enabled, per http://bugs.meego.com, are:
* American English (en_US)
* British English (en_GB)
* French (fr)
* Spanish (es)
* German (de)
* Italian (it)
* Polish (pl)
* Dutch (nl)
* Russian (ru)
* Swedish (sv)
* Finnish (fi)
* Brazilian-Portuguese (pt_BR)
* Canadian-French (fr_CA)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese Simplified (zh_CN)
* Chinese Traditional (zh_TW)

If in doubt of a language code, see here: http://www.transifex.net/languages/

[[Category: Localization]]

QtInternationalization

2011-06-14T18:31:13Z

Pmccarty: /* Translator comments */ update description of the "recommended" common practice

=Internationalization=

This is a developer's guide to internationalization (i18n) within the MeeGo UX project.

==Localizable Strings==

The most basic step in internationalization is to identify any user-visible strings in your application and replace them with code that looks up the appropriate string for the current locale. The way this is accomplished in Qt C++ code is to simply wrap the string with <code>tr()</code>:

<pre>QString label = tr("Ring tone:");</pre>

This is accomplished in Qt Quick (QML) code by wrapping the string with qsTr():

<pre>Text {
id: dialogTitle
text: qsTr("Find contacts")
...</pre>

There is a Qt command-line tool ''lupdate'' that scans source code for these <code>tr()</code> and <code>qsTr()</code> macros and pulls out the identified strings. It writes them into a ".ts file," an XML-format file that lists information about where the strings were found. In UX projects, we generate these TS files automatically when creating the dist tarball that we push to OBS.

Your top-level .pro file should have lines like these:

<pre>TRANSLATIONS += .qml lib/.h lib/*.cpp
PROJECT_NAME = meego-app-example

dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += git clone . $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION}/.git &&
dist.commands += rm -f $${PROJECT_NAME}-$${VERSION}/.gitignore &&
dist.commands += mkdir -p $${PROJECT_NAME}-$${VERSION}/ts &&
dist.commands += lupdate $${TRANSLATIONS} -ts $${PROJECT_NAME}-$${VERSION}/ts/$${PROJECT_NAME}.ts &&
dist.commands += tar jcpvf $${PROJECT_NAME}-$${VERSION}.tar.bz2 $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += echo; echo Created $${PROJECT_NAME}-$${VERSION}.tar.bz2</pre>

Make sure that <code>TRANSLATIONS</code> is set to include all files with translatable strings (you may need to include other subdirectories and .js files, for instance). Make sure that <code>PROJECT_NAME</code> is set to your application name.

Whenever you check in an update to OBS, you should create a clean tarball from git source. To create this tarball, run the following commands from the toplevel directory in your git tree:

<pre>$ qmake
$ make dist
</pre>

Then copy the generated tarball up to OBS. Bump the version up once a week. You should never submit an "sr" for the same version twice. But you can push to OBS multiple times throughout the week without doing an "sr."

Later these TS files are translated into various languages, and each one is compiled into a .qm binary file that allows efficient string lookup at runtime. Elsewhere you need to load a translator for each .qm file in your app, but this is handled automatically by our meego-qml-launcher for QML applications, so you generally don't have to think about. You just name your .ts file with your package name and it will be handled correctly.

==String Concatentation==

A common pitfall for i18n is building up strings by concatenation. You do this using assumptions about grammar and order that are true for your own language, but may not be true for another language. For example, consider this code:

<pre>function getBestPepperColor() {
return qsTr("red")
}

var message = qsTr("Tabasco is made from peppers selected using a ") + getBestPepperColor() + qsTr(" stick")</pre>

But in French, "red stick" is "bâton rouge". If you use concatenation as above, it will come out as "rouge bâton" in translation... incorrect!

So here's the solution:

<pre>var message = qsTr("Tabasco is made from peppers selected using a %1 stick").arg(getBestPepperColor())</pre>

Now the French translator will come up with something like:
<source>Tabasco est faite à partir de piments sélectionnés à l'aide d'un bâton %1.</source>
They are able to move the <code>%1</code> around to the right place for their language.

Another example is where there are multiple variables in the string. The order of the variables may need to change in translation. This cannot happen if you're concatenating.

Wrong:

<pre>// dateHeader will be e.g. "March 14th"
var dateHeader = getLocalizedMonth() + " " + getLocalizedDay()</pre>

This looks right because the month and day are localized, but in another language maybe the day needs to come first, like "14. Марта" in Russian.

Right:

<pre>// localized date header: %1 is month, %2 is day of month
var dateHeader = qsTr("%1 %2").arg(getLocalizedMonth()).arg(getLocalizedDay())</pre>

'''Note:''' There is a problem with the tools in QML in that the translator will only see "%1 %2" so they won't know what to do with it. In Qt, you can pass a second argument to tr() to give the translator a hint, for example:

<pre>QString dateFormat(tr("%1 %2", "%1 is the month, %2 is the day of the month"));
QString dateHeader = dateFormat.arg(getLocalizedMonth(), getLocalizedDay());</pre>

Also notice that the "<code>arg()</code>" function on QString can take multiple arguments, unlike in QML (to my knowledge).

==Translator comments==

Strings like "%1 %2" cannot get correctly translated by translators without knowing some context. It is possible to add a comment intended for translators to help them.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#translator-comments for more information.

In QML, a translator comment must be added to the line immediately preceding the affected string. For example:

<pre>//: This is a date range (start date - end date)
string: qsTr("%1 - %2")
</pre>

If two or more identical strings are used in a given QML source file, translator comments should be added to each of these strings. In addition, a second argument (of type <tt>string</tt> in QML) should be passed to <tt>qsTr()</tt> to ensure the source strings are treated as unique, translatable strings in the TS file. An example follows:

<pre>//: %1 is the number of transactions
text: qsTr("Total volume is %1", "transactions").arg(num)

//: %1 is the volume of water
text: qsTr("Total volume is %1", "watervolume").arg(vol)
</pre>

For an in-depth explanation, see http://lists.meego.com/pipermail/meego-il10n/2011-June/000516.html

==Disambiguation of strings ==

Imagine an application that uses the translatable string "Read" in one place as an action (e.g. a button that enables the user to read something), and in another place uses the translatable string "Read" to mark an element that has been read. The two different meanings (and translations to other languages) require disambiguation as otherwise they will end up as the same string in the translation files and can only receive exactly one translation that will be wrong in 50% of the cases.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#disambiguation for more information how to solve this.

==Plural handling==

Many languages have more than one plural form (e.g. Czech has one plural form for 2-4 and another one for >=5) or complex rules (e.g. Arabic uses the singular form for amounts of 1, 11, 21, 31, ...), hence code like
<pre>n == 1 ? tr("%n message saved") : tr("%n messages saved")</pre>
will fail for these languages.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#handling-plurals for more information how to solve this.

==Supported locales==

The locales which must be enabled, per http://bugs.meego.com, are:
* American English (en_US)
* British English (en_GB)
* French (fr)
* Spanish (es)
* German (de)
* Italian (it)
* Polish (pl)
* Dutch (nl)
* Russian (ru)
* Swedish (sv)
* Finnish (fi)
* Brazilian-Portuguese (pt_BR)
* Canadian-French (fr_CA)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese Simplified (zh_CN)
* Chinese Traditional (zh_TW)

If in doubt of a language code, see here: http://www.transifex.net/languages/

[[Category: Localization]]

Packaging/Guidelines

2011-06-02T05:17:21Z

Pmccarty: /* BuildRequires */ fix wikilink

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have a grace period for this data to be supplied and added to the build system. After the grace period, packages without a maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.131) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Explicit Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

Currently, only SystemV-style initscripts are supported in MeeGo.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

In the above .desktop file, <tt>[de]</tt> specifies the German language locale, covering any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.

'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

=== .desktop file post-install ===

After installing a .desktop file, it's typical to touch the file and the folder so that the UX will detect the change. Otherwise, the new file will not be detected until reboot. I.e.

%post
touch %{_datadir}/applications/foo.desktop
touch %{_datadir}/applications

...will update the time-stamp of the folder and the .desktop file.

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind that MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

Packaging/Guidelines

2011-06-02T04:56:48Z

Pmccarty: /* Maintaining a Package */ the latest `osc' version is now 0.131

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have a grace period for this data to be supplied and added to the build system. After the grace period, packages without a maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.131) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

Currently, only SystemV-style initscripts are supported in MeeGo.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

In the above .desktop file, <tt>[de]</tt> specifies the German language locale, covering any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.

'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

=== .desktop file post-install ===

After installing a .desktop file, it's typical to touch the file and the folder so that the UX will detect the change. Otherwise, the new file will not be detected until reboot. I.e.

%post
touch %{_datadir}/applications/foo.desktop
touch %{_datadir}/applications

...will update the time-stamp of the folder and the .desktop file.

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind that MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

Packaging/Guidelines

2011-06-02T04:55:09Z

Pmccarty: /* Maintaining a Package */ typos

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have a grace period for this data to be supplied and added to the build system. After the grace period, packages without a maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.130) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

Currently, only SystemV-style initscripts are supported in MeeGo.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

In the above .desktop file, <tt>[de]</tt> specifies the German language locale, covering any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.

'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

=== .desktop file post-install ===

After installing a .desktop file, it's typical to touch the file and the folder so that the UX will detect the change. Otherwise, the new file will not be detected until reboot. I.e.

%post
touch %{_datadir}/applications/foo.desktop
touch %{_datadir}/applications

...will update the time-stamp of the folder and the .desktop file.

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind that MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

Localization team

2011-05-28T08:40:31Z

Pmccarty: /* Information for translators */ avoid more underscores in wikilinks

These are the wikipages to discuss and plan the localization (L10N) and translation of MeeGo.

== Mission ==

The Localization working group defines the strategy for using crowd-sourcing for translating MeeGo into multiple languages, and observes its implementation. Using transifex.net as the tool, our goal is to build a community of dedicated translators, editors, reviewers, and testers in multiple languages.

== Localization Working Group ==

* [[LocalizationMeetings|Localization Meetings]]
* [[Transifex Roadmap]]
* [[String Freeze Policy]]

=== Tasks ===

(Note: This list might be partially outdated.)

The main areas within the scope of the working group are (in no particular order):

* Maemo/Moblin transition: bringing the best of localization policies, procedures, and best-known methods from maemo.org and moblin.org to meego.com
* Transifex administration: deciding where to host the tool, determining a team of admins and other users with special permissions, server administration
* Crowd-sourcing infrastructure: selection and administration of online tools for l10n community collaboration
* Creating and maintaining guides and guidelines for language translation teams
* Encouraging language translation teams

== Information for translators ==

MeeGo uses [https://meego.transifex.net/ Transifex] for translating.

* [[Language specific working groups|Translation teams (Language specific working groups) and contact information]]
* [[How to run a translation team]]
* [[Using Transifex]]

If you would like to have a language specific wikipage for your team, please create it under the namespace "Localization". Example: For the language with the language code xy, please create http://wiki.meego.com/Localization/Xy and link to it from [[Language specific working groups]].

== Information for software developers ==

* [[QML/Internationalisation|QML Internationalization]]
* [[QtInternationalization|Qt Internationalization]]
* [[GtkInternationalization|Gtk Internationalization]]

== Contact information ==

* [http://lists.meego.com/listinfo/meego-il10n meego-il10n mailing list] (You can also subscribe from your [https://meego.com/user/me/user_mailman_register account page on meego.com]).
* IRC: #meego-l10n on FreeNode IRC
* [[LocalizationMeetings|Meetings]]

== Other stuff ==

(Note: Content in this list might be outdated.)

* [[L10N_Chatter]]
* [[L10N/RoadmapProposal]]

== Contributors ==

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* [http://meego.com/users/margie Margie Foster] - I am the l10n project manager for MeeGo. Submitter of this proposal and happy to take an active role. Full disclosure: I am an [http://intel.com Intel] employee.
* [http://meego.com/users/glezos Dimitris Glezos] - I am the creator and lead developer for [http://www.transifex.net/ Transifex], the L10n tool powering the translations of [http://translate.moblin.org/ Moblin] and [http://www.transifex.net/collections/c/maemo-extras/ Maemo Extras], and also the L10n lead of the Fedora Project. I'd be happy to take an active role in the L10n engineering of MeeGo. Full disclosure: I am an [http://indifex.com/ Indifex] employee, the company sponsoring the development of Transifex.
* [http://meego.com/users/omaciel Og Maciel] - I am deeply involved with the translation efforts of several open source groups, including GNOME, Xfce, LXDE, Openbox, Moblin, and some minor contributions to KDE and Fedora. I'd be very interested to also take a more active role in the engineering and steering process of making MeeGo internationalized. Full disclosure: I am a big Transifex supporter (for many reasons) and am huge on quality control!
* [http://meego.com/users/milo Milo Casagrande] - I'm involved with different translation groups (Ubuntu, GNOME, and the Translation Project), and I'm leading the Italian Ubuntu translators group. I've made contributions also to Debian and Fedora, although I'm not really involved with them. I'd be happy to help this new L10n group.
* [http://meego.com/users/timeless timeless] - I maintain alternate translations of Maemo 4 and 5 for en_US and en_GB, which are also the basis for Mer. I've been on the periphery of l10n concerns, as a member of the [http://mozilla.org Mozilla community]. Full disclosure: I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/solt Marcin Sołtysiak] - [http://www.midgard-project.org/ Midgard]/MidCOM contributor and translator, [http://qaiku.com Qaiku] translator, [http://maemo.org/downloads/product/OS2008/os2008pl/ OS2008] (Chinook/Diablo) translator. Just a fan.
* [http://meego.com/users/amfidiusz Adrian Marcinkowski] - [http://invisionpower.com/ IP.Board] active developer & translator, [http://instantbird.com/ Instanbird] translator & beta tester. I'm familiar with working on Mercurial and SVN repositories as well as on po/pot files - and more than eager to help with l10n of MeeGo!
* [http://meego.com/users/Saviq Michał Sawicz] - In terms of translation, I've been involved in several L10n projects, Moblin being one of them. I have also revised the approach to L10n and L10n-related coding guidelines for the Elisa / Moovida project. I can help in both the core Localization Group and the Polish Localization Team.
* [http://meego.com/users/tjyrinki Timo Jyrinki] - L10n and I18N related work all-around. Ubuntu Finnish translators leader, GNOME translator, GNU translation project translator, Debian Developer, et cetera. Managed to also get involved with Moblin translations and related discussions before it became MeeGo.
* [http://meego.com/users/carvega Carmen Vega Reina] - I have coordinated localization projects for multifunctional devices (all-in-one printers, faxes, scanners),and in the past few years working on Symbian (mobile devices) L10n. I would like to learn and contribute to Meego. I have an extensive technical translation experience as well. I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/rodrigopadula Rodrigo Padula] - Fedora Brasil and LATAM founder and community manager by years,Fedora translator to pt_BR since many years ago. GNOME translator to pt_BR, GNOME contributor and GNOME Foundation Member, Mozilla Foundation contributor, Meego pt_BR translator and coordinator. I'm interested to help with L10n and I18N related tasks, community and contributor engagement efforts and everything that I can help to create a strong Meego community around the globe, specially in Brasil and Latin America.
* [http://wiki.meego.com/User:Andre Andre Klapper] - Too much; just click the link. :-)

== Related pages ==

A complete list of the pages in this space can be found in the [[:Category:Localization|localization category]].

[[Category:Localization]]

Localization team

2011-05-28T08:39:25Z

Pmccarty: /* Information for translators */ simplify more wikilinks, for ease of editing

These are the wikipages to discuss and plan the localization (L10N) and translation of MeeGo.

== Mission ==

The Localization working group defines the strategy for using crowd-sourcing for translating MeeGo into multiple languages, and observes its implementation. Using transifex.net as the tool, our goal is to build a community of dedicated translators, editors, reviewers, and testers in multiple languages.

== Localization Working Group ==

* [[LocalizationMeetings|Localization Meetings]]
* [[Transifex Roadmap]]
* [[String Freeze Policy]]

=== Tasks ===

(Note: This list might be partially outdated.)

The main areas within the scope of the working group are (in no particular order):

* Maemo/Moblin transition: bringing the best of localization policies, procedures, and best-known methods from maemo.org and moblin.org to meego.com
* Transifex administration: deciding where to host the tool, determining a team of admins and other users with special permissions, server administration
* Crowd-sourcing infrastructure: selection and administration of online tools for l10n community collaboration
* Creating and maintaining guides and guidelines for language translation teams
* Encouraging language translation teams

== Information for translators ==

MeeGo uses [https://meego.transifex.net/ Transifex] for translating.

* [[Language specific working groups|Translation teams (Language specific working groups) and contact information]]
* [[How to run a translation team]]
* [[Using Transifex]]

If you would like to have a language specific wikipage for your team, please create it under the namespace "Localization". Example: For the language with the language code xy, please create http://wiki.meego.com/Localization/Xy and link to it from [[Language_specific_working_groups]].

== Information for software developers ==

* [[QML/Internationalisation|QML Internationalization]]
* [[QtInternationalization|Qt Internationalization]]
* [[GtkInternationalization|Gtk Internationalization]]

== Contact information ==

* [http://lists.meego.com/listinfo/meego-il10n meego-il10n mailing list] (You can also subscribe from your [https://meego.com/user/me/user_mailman_register account page on meego.com]).
* IRC: #meego-l10n on FreeNode IRC
* [[LocalizationMeetings|Meetings]]

== Other stuff ==

(Note: Content in this list might be outdated.)

* [[L10N_Chatter]]
* [[L10N/RoadmapProposal]]

== Contributors ==

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* [http://meego.com/users/margie Margie Foster] - I am the l10n project manager for MeeGo. Submitter of this proposal and happy to take an active role. Full disclosure: I am an [http://intel.com Intel] employee.
* [http://meego.com/users/glezos Dimitris Glezos] - I am the creator and lead developer for [http://www.transifex.net/ Transifex], the L10n tool powering the translations of [http://translate.moblin.org/ Moblin] and [http://www.transifex.net/collections/c/maemo-extras/ Maemo Extras], and also the L10n lead of the Fedora Project. I'd be happy to take an active role in the L10n engineering of MeeGo. Full disclosure: I am an [http://indifex.com/ Indifex] employee, the company sponsoring the development of Transifex.
* [http://meego.com/users/omaciel Og Maciel] - I am deeply involved with the translation efforts of several open source groups, including GNOME, Xfce, LXDE, Openbox, Moblin, and some minor contributions to KDE and Fedora. I'd be very interested to also take a more active role in the engineering and steering process of making MeeGo internationalized. Full disclosure: I am a big Transifex supporter (for many reasons) and am huge on quality control!
* [http://meego.com/users/milo Milo Casagrande] - I'm involved with different translation groups (Ubuntu, GNOME, and the Translation Project), and I'm leading the Italian Ubuntu translators group. I've made contributions also to Debian and Fedora, although I'm not really involved with them. I'd be happy to help this new L10n group.
* [http://meego.com/users/timeless timeless] - I maintain alternate translations of Maemo 4 and 5 for en_US and en_GB, which are also the basis for Mer. I've been on the periphery of l10n concerns, as a member of the [http://mozilla.org Mozilla community]. Full disclosure: I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/solt Marcin Sołtysiak] - [http://www.midgard-project.org/ Midgard]/MidCOM contributor and translator, [http://qaiku.com Qaiku] translator, [http://maemo.org/downloads/product/OS2008/os2008pl/ OS2008] (Chinook/Diablo) translator. Just a fan.
* [http://meego.com/users/amfidiusz Adrian Marcinkowski] - [http://invisionpower.com/ IP.Board] active developer & translator, [http://instantbird.com/ Instanbird] translator & beta tester. I'm familiar with working on Mercurial and SVN repositories as well as on po/pot files - and more than eager to help with l10n of MeeGo!
* [http://meego.com/users/Saviq Michał Sawicz] - In terms of translation, I've been involved in several L10n projects, Moblin being one of them. I have also revised the approach to L10n and L10n-related coding guidelines for the Elisa / Moovida project. I can help in both the core Localization Group and the Polish Localization Team.
* [http://meego.com/users/tjyrinki Timo Jyrinki] - L10n and I18N related work all-around. Ubuntu Finnish translators leader, GNOME translator, GNU translation project translator, Debian Developer, et cetera. Managed to also get involved with Moblin translations and related discussions before it became MeeGo.
* [http://meego.com/users/carvega Carmen Vega Reina] - I have coordinated localization projects for multifunctional devices (all-in-one printers, faxes, scanners),and in the past few years working on Symbian (mobile devices) L10n. I would like to learn and contribute to Meego. I have an extensive technical translation experience as well. I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/rodrigopadula Rodrigo Padula] - Fedora Brasil and LATAM founder and community manager by years,Fedora translator to pt_BR since many years ago. GNOME translator to pt_BR, GNOME contributor and GNOME Foundation Member, Mozilla Foundation contributor, Meego pt_BR translator and coordinator. I'm interested to help with L10n and I18N related tasks, community and contributor engagement efforts and everything that I can help to create a strong Meego community around the globe, specially in Brasil and Latin America.
* [http://wiki.meego.com/User:Andre Andre Klapper] - Too much; just click the link. :-)

== Related pages ==

A complete list of the pages in this space can be found in the [[:Category:Localization|localization category]].

[[Category:Localization]]

LocalizationMeetings

2011-05-28T08:37:09Z

Pmccarty: /* Logistics */ wikify section link and remove abbreviation for 'hours'

== Logistics ==

Meetings normally take place monthly on Wednesdays at 15:00 UTC.

All MeeGo QA meetings take place in the MeeGo IRC channels on freenode:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-l10n
Propose a topic in advance by editing this page ([[#Next Meeting]]). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18 hours before the meeting. If there is too many items then V-PV will pick the topics to be discussed.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==

To be announced.

== Logs ==

Note: The format of this list is YYYY-MM-DD (Year-Month-Day).

* 2011-01-26: [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.html Summary]
* 2010-11-04: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html Summary]
* 2010-10-14: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html Summary]
* 2010-09-23: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html Summary]
* 2010-09-09: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt Summary]
* 2010-08-19: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt Summary]
* 2010-07-29: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html Summary]
* 2010-07-15: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html Summary]
* 2010-07-01: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html Summary]
* 2010-06-17: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html Summary]
* 2010-06-03: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html Summary]
* 2010-04-19: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html Summary]
* [[L10N_BOF_at_the_Collaboration_Summit|Some ramblings from the BOF at the Collaboration summit the week before]]
* 2010-04-02: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html Summary], [[L10n_plan|L10N plan update]]
* 2010-03-19: [[L10N_IRC_Meeting_20100319|Full log]], [[L10N_IRC_Meeting_20100319_Summary|Summary]], [[L10n_plan|L10N plan update]]
* 2010-03-05: [[L10N_IRC_Meeting_20100305|Full log]], [[L10N_IRC_Meeting_20100305_Summary|Summary]]

[[Category:Localization]]

LocalizationMeetings

2011-05-28T08:35:00Z

Pmccarty: /* Logistics */ clarify where IRC meetings take place

== Logistics ==

Meetings normally take place monthly on Wednesdays at 15:00 UTC.

All MeeGo QA meetings take place in the MeeGo IRC channels on freenode:
* Main meeting: #meego-meeting
* Back channel & other discussions (optional): #meego-l10n
Propose a topic in advance by editing this page (#Next Meeting). Please note the following before proposing a topic:
* Your topic proposal contains a title linking to a relevant page, and the names of the team or individuals proposing that topic.
* The people behind the proposal need to take part in the MeeGo QA meeting.
Resolution - Agenda is frozen approximately 18h before the meeting. If there is too many items then V-PV will pick the topics to be discussed.
* Topics proposed might be addressed through other channels as well, being answered through other channels or being forwarded to the right team.

== Next Meeting ==

To be announced.

== Logs ==

Note: The format of this list is YYYY-MM-DD (Year-Month-Day).

* 2011-01-26: [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.html Summary]
* 2010-11-04: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html Summary]
* 2010-10-14: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html Summary]
* 2010-09-23: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html Summary]
* 2010-09-09: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt Summary]
* 2010-08-19: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt Summary]
* 2010-07-29: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html Summary]
* 2010-07-15: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html Summary]
* 2010-07-01: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html Summary]
* 2010-06-17: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html Summary]
* 2010-06-03: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html Summary]
* 2010-04-19: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html Summary]
* [[L10N_BOF_at_the_Collaboration_Summit|Some ramblings from the BOF at the Collaboration summit the week before]]
* 2010-04-02: [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html Full log], [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html Summary], [[L10n_plan|L10N plan update]]
* 2010-03-19: [[L10N_IRC_Meeting_20100319|Full log]], [[L10N_IRC_Meeting_20100319_Summary|Summary]], [[L10n_plan|L10N plan update]]
* 2010-03-05: [[L10N_IRC_Meeting_20100305|Full log]], [[L10N_IRC_Meeting_20100305_Summary|Summary]]

[[Category:Localization]]

String Freeze Policy

2011-05-28T08:33:52Z

Pmccarty: fix some more wikilinks

This is a proposal for the l10n community to agree on and then submit to the developer community for their buy-in. I'd like to see this as part of the developer guidelines, [[Developer Guide]] and part of the release cycle [[Release Engineering/Release Timeline]].

As of the string freeze for a release, no new strings or modification of existing strings marked for translation are allowed for any MeeGo package that is translated from the MeeGo Open Source Project (ie. ones that MeeGo is upstream for). The purpose of the string freeze is to help ensure high quality translations in the final release, by giving translators adequate time to finish their work and to guarantee that this work will end up in the final release.

A string freeze is a date when translatable strings and user interfaces are frozen. No new strings can be added or existing ones modified from this date to the release.

The string freeze is mandatory so that translators have an adequate amount of time to do their work (so they longer need to chase a moving target). String freeze is part of the process that takes place in preparation for the release.

= What changes are affected by the string freeze? =

MeeGo string freezes affect the packages that MeeGo is upstream for which are included in a release. Please see http://meego.transifex.net for a list of MeeGo projects.

Any addition or change of a string marked for translation (either by gettext or by intltool) in one of these modules is affected by the freeze, apart from the exceptions listed below, and will need announcement and subsequent approval. This is true even for bug fixes that change or alter translatable strings.

= What changes are not affected by the string freeze? =

* Change or addition of a message that is not marked for translation.
* Removal of a translatable string.
* Addition of a comment aimed for translators.
* Addition of a translatable message (or change a translatable message into a message) that is absolutely identical to an existing message that is already marked for translation, and that has the same meaning and context. Then the existing translation will automatically be re-used.

The following types of changes do not need explicit approval, however we would still very much like them to be announced so that we know about them:

* Marking a message for translation that was previously not marked for translation by accident.
* Adding a file to POTFILES.in that was previously not included in POTFILES.in by accident.

= What should I do before the string freeze starts? =

* Make sure that your resource (application or documentation) is complete as far as translatable strings are concerned.
* Make sure that your module's po/POTFILES.in and po/POTFILES.skip (or any other way you use to choose your translatable files) are correct and up2date and that no source files are lacking from them. Use the command intltool-update --maintain in the po directory to verify.
* Try to resolve as many bugs with the keyword "string" in Bugzilla as you can. The string freeze is not intended to be a "string fixing period" -- please do such work before the string freeze, since that facilitates the work for everyone.

= Breaking the freeze =

If you think that you need to break the string freeze, then you should ask for approval from the MeeGo Localization Team prior to breaking the freeze. To do so, send an email to il10n@meego.com and CC meego-releases@meego.com with the following information:
* A description of what you want to change
* Rationale for why the change is important enough to be allowed in after the string freeze
* Impact of *not* accepting the string at this point of the schedule

The MeeGo L10n Steering Committee (potentially with the release team) will evaluate the request and provide feedback. If the string change is rejected, then you'll have to wait for the next development cycle to begin to get the change into MeeGo packages. Disputes over rejected changes can be escalated to TSG.

Note that ignoring the freeze process and introducing new strings anyway may lead to your package being reverted and a reduction of the chances of an exception being made.

[[Category: Localization]]

String Freeze Policy

2011-05-28T08:32:25Z

Pmccarty: /* What changes are affected by the string freeze? */ remove example hyperlink

This is a proposal for the l10n community to agree on and then submit to the developer community for their buy-in. I'd like to see this as part of the developer guidelines, [[Developer_Guide]] and part of the release cycle [[Release_Engineering/Release_Timeline]].

As of the string freeze for a release, no new strings or modification of existing strings marked for translation are allowed for any MeeGo package that is translated from the MeeGo Open Source Project (ie. ones that MeeGo is upstream for). The purpose of the string freeze is to help ensure high quality translations in the final release, by giving translators adequate time to finish their work and to guarantee that this work will end up in the final release.

A string freeze is a date when translatable strings and user interfaces are frozen. No new strings can be added or existing ones modified from this date to the release.

The string freeze is mandatory so that translators have an adequate amount of time to do their work (so they longer need to chase a moving target). String freeze is part of the process that takes place in preparation for the release.

= What changes are affected by the string freeze? =

MeeGo string freezes affect the packages that MeeGo is upstream for which are included in a release. Please see http://meego.transifex.net for a list of MeeGo projects.

Any addition or change of a string marked for translation (either by gettext or by intltool) in one of these modules is affected by the freeze, apart from the exceptions listed below, and will need announcement and subsequent approval. This is true even for bug fixes that change or alter translatable strings.

= What changes are not affected by the string freeze? =

* Change or addition of a message that is not marked for translation.
* Removal of a translatable string.
* Addition of a comment aimed for translators.
* Addition of a translatable message (or change a translatable message into a message) that is absolutely identical to an existing message that is already marked for translation, and that has the same meaning and context. Then the existing translation will automatically be re-used.

The following types of changes do not need explicit approval, however we would still very much like them to be announced so that we know about them:

* Marking a message for translation that was previously not marked for translation by accident.
* Adding a file to POTFILES.in that was previously not included in POTFILES.in by accident.

= What should I do before the string freeze starts? =

* Make sure that your resource (application or documentation) is complete as far as translatable strings are concerned.
* Make sure that your module's po/POTFILES.in and po/POTFILES.skip (or any other way you use to choose your translatable files) are correct and up2date and that no source files are lacking from them. Use the command intltool-update --maintain in the po directory to verify.
* Try to resolve as many bugs with the keyword "string" in Bugzilla as you can. The string freeze is not intended to be a "string fixing period" -- please do such work before the string freeze, since that facilitates the work for everyone.

= Breaking the freeze =

If you think that you need to break the string freeze, then you should ask for approval from the MeeGo Localization Team prior to breaking the freeze. To do so, send an email to il10n@meego.com and CC meego-releases@meego.com with the following information:
* A description of what you want to change
* Rationale for why the change is important enough to be allowed in after the string freeze
* Impact of *not* accepting the string at this point of the schedule

The MeeGo L10n Steering Committee (potentially with the release team) will evaluate the request and provide feedback. If the string change is rejected, then you'll have to wait for the next development cycle to begin to get the change into MeeGo packages. Disputes over rejected changes can be escalated to TSG.

Note that ignoring the freeze process and introducing new strings anyway may lead to your package being reverted and a reduction of the chances of an exception being made.

[[Category: Localization]]

Localization team

2011-05-28T08:30:48Z

Pmccarty: /* Localization Working Group */ make these wikilinks more readable

These are the wikipages to discuss and plan the localization (L10N) and translation of MeeGo.

== Mission ==

The Localization working group defines the strategy for using crowd-sourcing for translating MeeGo into multiple languages, and observes its implementation. Using transifex.net as the tool, our goal is to build a community of dedicated translators, editors, reviewers, and testers in multiple languages.

== Localization Working Group ==

* [[LocalizationMeetings|Localization Meetings]]
* [[Transifex Roadmap]]
* [[String Freeze Policy]]

=== Tasks ===

(Note: This list might be partially outdated.)

The main areas within the scope of the working group are (in no particular order):

* Maemo/Moblin transition: bringing the best of localization policies, procedures, and best-known methods from maemo.org and moblin.org to meego.com
* Transifex administration: deciding where to host the tool, determining a team of admins and other users with special permissions, server administration
* Crowd-sourcing infrastructure: selection and administration of online tools for l10n community collaboration
* Creating and maintaining guides and guidelines for language translation teams
* Encouraging language translation teams

== Information for translators ==

MeeGo uses [http://meego.transifex.net/ Transifex] for translating.

* [[Language_specific_working_groups|Translation teams (Language specific working groups) and contact information]]
* [[How_to_run_a_translation_team|How to run a translation team]]
* [[Using_Transifex|Using Transifex]]

If you would like to have a language specific wikipage for your team, please create it under the namespace "Localization". Example: For the language with the language code xy, please create http://wiki.meego.com/Localization/Xy and link to it from [[Language_specific_working_groups]].

== Information for software developers ==

* [[QML/Internationalisation|QML Internationalization]]
* [[QtInternationalization|Qt Internationalization]]
* [[GtkInternationalization|Gtk Internationalization]]

== Contact information ==

* [http://lists.meego.com/listinfo/meego-il10n meego-il10n mailing list] (You can also subscribe from your [https://meego.com/user/me/user_mailman_register account page on meego.com]).
* IRC: #meego-l10n on FreeNode IRC
* [[LocalizationMeetings|Meetings]]

== Other stuff ==

(Note: Content in this list might be outdated.)

* [[L10N_Chatter]]
* [[L10N/RoadmapProposal]]

== Contributors ==

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* [http://meego.com/users/margie Margie Foster] - I am the l10n project manager for MeeGo. Submitter of this proposal and happy to take an active role. Full disclosure: I am an [http://intel.com Intel] employee.
* [http://meego.com/users/glezos Dimitris Glezos] - I am the creator and lead developer for [http://www.transifex.net/ Transifex], the L10n tool powering the translations of [http://translate.moblin.org/ Moblin] and [http://www.transifex.net/collections/c/maemo-extras/ Maemo Extras], and also the L10n lead of the Fedora Project. I'd be happy to take an active role in the L10n engineering of MeeGo. Full disclosure: I am an [http://indifex.com/ Indifex] employee, the company sponsoring the development of Transifex.
* [http://meego.com/users/omaciel Og Maciel] - I am deeply involved with the translation efforts of several open source groups, including GNOME, Xfce, LXDE, Openbox, Moblin, and some minor contributions to KDE and Fedora. I'd be very interested to also take a more active role in the engineering and steering process of making MeeGo internationalized. Full disclosure: I am a big Transifex supporter (for many reasons) and am huge on quality control!
* [http://meego.com/users/milo Milo Casagrande] - I'm involved with different translation groups (Ubuntu, GNOME, and the Translation Project), and I'm leading the Italian Ubuntu translators group. I've made contributions also to Debian and Fedora, although I'm not really involved with them. I'd be happy to help this new L10n group.
* [http://meego.com/users/timeless timeless] - I maintain alternate translations of Maemo 4 and 5 for en_US and en_GB, which are also the basis for Mer. I've been on the periphery of l10n concerns, as a member of the [http://mozilla.org Mozilla community]. Full disclosure: I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/solt Marcin Sołtysiak] - [http://www.midgard-project.org/ Midgard]/MidCOM contributor and translator, [http://qaiku.com Qaiku] translator, [http://maemo.org/downloads/product/OS2008/os2008pl/ OS2008] (Chinook/Diablo) translator. Just a fan.
* [http://meego.com/users/amfidiusz Adrian Marcinkowski] - [http://invisionpower.com/ IP.Board] active developer & translator, [http://instantbird.com/ Instanbird] translator & beta tester. I'm familiar with working on Mercurial and SVN repositories as well as on po/pot files - and more than eager to help with l10n of MeeGo!
* [http://meego.com/users/Saviq Michał Sawicz] - In terms of translation, I've been involved in several L10n projects, Moblin being one of them. I have also revised the approach to L10n and L10n-related coding guidelines for the Elisa / Moovida project. I can help in both the core Localization Group and the Polish Localization Team.
* [http://meego.com/users/tjyrinki Timo Jyrinki] - L10n and I18N related work all-around. Ubuntu Finnish translators leader, GNOME translator, GNU translation project translator, Debian Developer, et cetera. Managed to also get involved with Moblin translations and related discussions before it became MeeGo.
* [http://meego.com/users/carvega Carmen Vega Reina] - I have coordinated localization projects for multifunctional devices (all-in-one printers, faxes, scanners),and in the past few years working on Symbian (mobile devices) L10n. I would like to learn and contribute to Meego. I have an extensive technical translation experience as well. I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/rodrigopadula Rodrigo Padula] - Fedora Brasil and LATAM founder and community manager by years,Fedora translator to pt_BR since many years ago. GNOME translator to pt_BR, GNOME contributor and GNOME Foundation Member, Mozilla Foundation contributor, Meego pt_BR translator and coordinator. I'm interested to help with L10n and I18N related tasks, community and contributor engagement efforts and everything that I can help to create a strong Meego community around the globe, specially in Brasil and Latin America.
* [http://wiki.meego.com/User:Andre Andre Klapper] - Too much; just click the link. :-)

== Related pages ==

A complete list of the pages in this space can be found in the [[:Category:Localization|localization category]].

[[Category:Localization]]

QtInternationalization

2011-05-11T20:28:09Z

Pmccarty: /* Translator comments */ add more information about best practice for QML code.

=Internationalization=

This is a developer's guide to internationalization (i18n) within the MeeGo UX project.

==Localizable Strings==

The most basic step in internationalization is to identify any user-visible strings in your application and replace them with code that looks up the appropriate string for the current locale. The way this is accomplished in Qt C++ code is to simply wrap the string with <code>tr()</code>:

<pre>QString label = tr("Ring tone:");</pre>

This is accomplished in Qt Quick (QML) code by wrapping the string with qsTr():

<pre>Text {
id: dialogTitle
text: qsTr("Find contacts")
...</pre>

There is a Qt command-line tool ''lupdate'' that scans source code for these <code>tr()</code> and <code>qsTr()</code> macros and pulls out the identified strings. It writes them into a ".ts file," an XML-format file that lists information about where the strings were found. In UX projects, we generate these TS files automatically when creating the dist tarball that we push to OBS.

Your top-level .pro file should have lines like these:

<pre>TRANSLATIONS += .qml lib/.h lib/*.cpp
PROJECT_NAME = meego-app-example

dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += git clone . $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION}/.git &&
dist.commands += rm -f $${PROJECT_NAME}-$${VERSION}/.gitignore &&
dist.commands += mkdir -p $${PROJECT_NAME}-$${VERSION}/ts &&
dist.commands += lupdate $${TRANSLATIONS} -ts $${PROJECT_NAME}-$${VERSION}/ts/$${PROJECT_NAME}.ts &&
dist.commands += tar jcpvf $${PROJECT_NAME}-$${VERSION}.tar.bz2 $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += echo; echo Created $${PROJECT_NAME}-$${VERSION}.tar.bz2</pre>

Make sure that <code>TRANSLATIONS</code> is set to include all files with translatable strings (you may need to include other subdirectories and .js files, for instance). Make sure that <code>PROJECT_NAME</code> is set to your application name.

Whenever you check in an update to OBS, you should create a clean tarball from git source. To create this tarball, run the following commands from the toplevel directory in your git tree:

<pre>$ qmake
$ make dist
</pre>

Then copy the generated tarball up to OBS. Bump the version up once a week. You should never submit an "sr" for the same version twice. But you can push to OBS multiple times throughout the week without doing an "sr."

Later these TS files are translated into various languages, and each one is compiled into a .qm binary file that allows efficient string lookup at runtime. Elsewhere you need to load a translator for each .qm file in your app, but this is handled automatically by our meego-qml-launcher for QML applications, so you generally don't have to think about. You just name your .ts file with your package name and it will be handled correctly.

==String Concatentation==

A common pitfall for i18n is building up strings by concatenation. You do this using assumptions about grammar and order that are true for your own language, but may not be true for another language. For example, consider this code:

<pre>function getBestPepperColor() {
return qsTr("red")
}

var message = qsTr("Tabasco is made from peppers selected using a ") + getBestPepperColor() + qsTr(" stick")</pre>

But in French, "red stick" is "bâton rouge". If you use concatenation as above, it will come out as "rouge bâton" in translation... incorrect!

So here's the solution:

<pre>var message = qsTr("Tabasco is made from peppers selected using a %1 stick").arg(getBestPepperColor())</pre>

Now the French translator will come up with something like:
<source>Tabasco est faite à partir de piments sélectionnés à l'aide d'un bâton %1.</source>
They are able to move the <code>%1</code> around to the right place for their language.

Another example is where there are multiple variables in the string. The order of the variables may need to change in translation. This cannot happen if you're concatenating.

Wrong:

<pre>// dateHeader will be e.g. "March 14th"
var dateHeader = getLocalizedMonth() + " " + getLocalizedDay()</pre>

This looks right because the month and day are localized, but in another language maybe the day needs to come first, like "14. Марта" in Russian.

Right:

<pre>// localized date header: %1 is month, %2 is day of month
var dateHeader = qsTr("%1 %2").arg(getLocalizedMonth()).arg(getLocalizedDay())</pre>

'''Note:''' There is a problem with the tools in QML in that the translator will only see "%1 %2" so they won't know what to do with it. In Qt, you can pass a second argument to tr() to give the translator a hint, for example:

<pre>QString dateFormat(tr("%1 %2", "%1 is the month, %2 is the day of the month"));
QString dateHeader = dateFormat.arg(getLocalizedMonth(), getLocalizedDay());</pre>

Also notice that the "<code>arg()</code>" function on QString can take multiple arguments, unlike in QML (to my knowledge).

==Translator comments==

Strings like "%1 %2" cannot get correctly translated by translators without knowing some context. It is possible to add a comment intended for translators to help them.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#translator-comments for more information.

In QML, it is possible to pass a comment string as the second argument to <tt>qsTr()</tt>, but this is ''strongly'' discouraged due to the lack of documentation. Compare the two forms below:

Discouraged:

<pre>string: qsTr("%1 - %2", "This is a date range (start date - end date)")</pre>

Recommended:

<pre>//: This is a date range (start date - end date)
string: qsTr("%1 - %2")
</pre>

==Disambiguation of strings ==

Imagine an application that uses the translatable string "Read" in one place as an action (e.g. a button that enables the user to read something), and in another place uses the translatable string "Read" to mark an element that has been read. The two different meanings (and translations to other languages) require disambiguation as otherwise they will end up as the same string in the translation files and can only receive exactly one translation that will be wrong in 50% of the cases.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#disambiguation for more information how to solve this.

==Plural handling==

Many languages have more than one plural form (e.g. Czech has one plural form for 2-4 and another one for >=5) or complex rules (e.g. Arabic uses the singular form for amounts of 1, 11, 21, 31, ...), hence code like
<pre>n == 1 ? tr("%n message saved") : tr("%n messages saved")</pre>
will fail for these languages.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#handling-plurals for more information how to solve this.

==Supported locales==

The locales which must be enabled, per http://bugs.meego.com, are:
* American English (en_US)
* British English (en_GB)
* French (fr)
* Spanish (es)
* German (de)
* Italian (it)
* Polish (pl)
* Dutch (nl)
* Russian (ru)
* Swedish (sv)
* Finnish (fi)
* Brazilian-Portuguese (pt_BR)
* Canadian-French (fr_CA)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese Simplified (zh_CN)
* Chinese Traditional (zh_TW)

If in doubt of a language code, see here: http://www.transifex.net/languages/

[[Category: Localization]]

QtInternationalization

2011-05-11T17:26:47Z

Pmccarty: /* Localizable Strings */ clarify `make dist' process

=Internationalization=

This is a developer's guide to internationalization (i18n) within the MeeGo UX project.

==Localizable Strings==

The most basic step in internationalization is to identify any user-visible strings in your application and replace them with code that looks up the appropriate string for the current locale. The way this is accomplished in Qt C++ code is to simply wrap the string with <code>tr()</code>:

<pre>QString label = tr("Ring tone:");</pre>

This is accomplished in Qt Quick (QML) code by wrapping the string with qsTr():

<pre>Text {
id: dialogTitle
text: qsTr("Find contacts")
...</pre>

There is a Qt command-line tool ''lupdate'' that scans source code for these <code>tr()</code> and <code>qsTr()</code> macros and pulls out the identified strings. It writes them into a ".ts file," an XML-format file that lists information about where the strings were found. In UX projects, we generate these TS files automatically when creating the dist tarball that we push to OBS.

Your top-level .pro file should have lines like these:

<pre>TRANSLATIONS += .qml lib/.h lib/*.cpp
PROJECT_NAME = meego-app-example

dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += git clone . $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION}/.git &&
dist.commands += rm -f $${PROJECT_NAME}-$${VERSION}/.gitignore &&
dist.commands += mkdir -p $${PROJECT_NAME}-$${VERSION}/ts &&
dist.commands += lupdate $${TRANSLATIONS} -ts $${PROJECT_NAME}-$${VERSION}/ts/$${PROJECT_NAME}.ts &&
dist.commands += tar jcpvf $${PROJECT_NAME}-$${VERSION}.tar.bz2 $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += echo; echo Created $${PROJECT_NAME}-$${VERSION}.tar.bz2</pre>

Make sure that <code>TRANSLATIONS</code> is set to include all files with translatable strings (you may need to include other subdirectories and .js files, for instance). Make sure that <code>PROJECT_NAME</code> is set to your application name.

Whenever you check in an update to OBS, you should create a clean tarball from git source. To create this tarball, run the following commands from the toplevel directory in your git tree:

<pre>$ qmake
$ make dist
</pre>

Then copy the generated tarball up to OBS. Bump the version up once a week. You should never submit an "sr" for the same version twice. But you can push to OBS multiple times throughout the week without doing an "sr."

Later these TS files are translated into various languages, and each one is compiled into a .qm binary file that allows efficient string lookup at runtime. Elsewhere you need to load a translator for each .qm file in your app, but this is handled automatically by our meego-qml-launcher for QML applications, so you generally don't have to think about. You just name your .ts file with your package name and it will be handled correctly.

==String Concatentation==

A common pitfall for i18n is building up strings by concatenation. You do this using assumptions about grammar and order that are true for your own language, but may not be true for another language. For example, consider this code:

<pre>function getBestPepperColor() {
return qsTr("red")
}

var message = qsTr("Tabasco is made from peppers selected using a ") + getBestPepperColor() + qsTr(" stick")</pre>

But in French, "red stick" is "bâton rouge". If you use concatenation as above, it will come out as "rouge bâton" in translation... incorrect!

So here's the solution:

<pre>var message = qsTr("Tabasco is made from peppers selected using a %1 stick").arg(getBestPepperColor())</pre>

Now the French translator will come up with something like:
<source>Tabasco est faite à partir de piments sélectionnés à l'aide d'un bâton %1.</source>
They are able to move the <code>%1</code> around to the right place for their language.

Another example is where there are multiple variables in the string. The order of the variables may need to change in translation. This cannot happen if you're concatenating.

Wrong:

<pre>// dateHeader will be e.g. "March 14th"
var dateHeader = getLocalizedMonth() + " " + getLocalizedDay()</pre>

This looks right because the month and day are localized, but in another language maybe the day needs to come first, like "14. Марта" in Russian.

Right:

<pre>// localized date header: %1 is month, %2 is day of month
var dateHeader = qsTr("%1 %2").arg(getLocalizedMonth()).arg(getLocalizedDay())</pre>

'''Note:''' There is a problem with the tools in QML in that the translator will only see "%1 %2" so they won't know what to do with it. In Qt, you can pass a second argument to tr() to give the translator a hint, for example:

<pre>QString dateFormat(tr("%1 %2", "%1 is the month, %2 is the day of the month"));
QString dateHeader = dateFormat.arg(getLocalizedMonth(), getLocalizedDay());</pre>

Also notice that the "<code>arg()</code>" function on QString can take multiple arguments, unlike in QML (to my knowledge).

==Translator comments==

Strings like "%1 %2" cannot get correctly translated by translators without knowing some context. It is possible to add a comment intended for translators to help them.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#translator-comments for more information.

==Disambiguation of strings ==

Imagine an application that uses the translatable string "Read" in one place as an action (e.g. a button that enables the user to read something), and in another place uses the translatable string "Read" to mark an element that has been read. The two different meanings (and translations to other languages) require disambiguation as otherwise they will end up as the same string in the translation files and can only receive exactly one translation that will be wrong in 50% of the cases.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#disambiguation for more information how to solve this.

==Plural handling==

Many languages have more than one plural form (e.g. Czech has one plural form for 2-4 and another one for >=5) or complex rules (e.g. Arabic uses the singular form for amounts of 1, 11, 21, 31, ...), hence code like
<pre>n == 1 ? tr("%n message saved") : tr("%n messages saved")</pre>
will fail for these languages.

See http://doc.qt.nokia.com/latest/i18n-source-translation.html#handling-plurals for more information how to solve this.

==Supported locales==

The locales which must be enabled, per http://bugs.meego.com, are:
* American English (en_US)
* British English (en_GB)
* French (fr)
* Spanish (es)
* German (de)
* Italian (it)
* Polish (pl)
* Dutch (nl)
* Russian (ru)
* Swedish (sv)
* Finnish (fi)
* Brazilian-Portuguese (pt_BR)
* Canadian-French (fr_CA)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese Simplified (zh_CN)
* Chinese Traditional (zh_TW)

If in doubt of a language code, see here: http://www.transifex.net/languages/

[[Category: Localization]]

Packaging/Guidelines

2011-05-10T17:46:13Z

Pmccarty: /* Localizing .desktop files */ grammar

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have agrace period for this data to be supplied and added to the build system. After the grace period, packages without maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.130) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

Currently, only SystemV-style initscripts are supported in MeeGo.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

In the above .desktop file, <tt>[de]</tt> specifies the German language locale, covering any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.

'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind theat MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

Packaging/Guidelines

2011-05-10T17:45:25Z

Pmccarty: /* Localizing .desktop files */ add some more notes

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have agrace period for this data to be supplied and added to the build system. After the grace period, packages without maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.130) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

Currently, only SystemV-style initscripts are supported in MeeGo.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

In the above .desktop file, <tt>[de]</tt> specifies the German language locale, and logically covers any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.

'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind theat MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

Packaging/Guidelines

2011-05-10T17:26:08Z

Pmccarty: /* Desktop files */ add a section for desktop file localization

= Packaging Guidelines =

Guidelines below were adapted for MeeGo from Moblin, OpenSUSE, Fedora and other distributions.

== Maintaining a Package ==
Every package in MeeGo needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from MeeGo. A package maintainer is responsible for making sure that
* packages are up to date with latest upstream
* packages consistently build in the MeeGo build system and fix build failures when they occur
* package meta data in the RPM spec file is accurate
* the license of the package is correct
* she/he follow upstream for any critical security issues and fix them ASAP
* she/he Provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues

Since the data about ownership of packages is not maintained anywhere right now we are starting to use available meta data fields in the build system to track ownership. This will be better integrated and managed at a later point, but to be able to start somewhere MeeGo will use the bugowner key available for every package. We will start adding the metadata about maintainers (bugowners) in the build system and we will have agrace period for this data to be supplied and added to the build system. After the grace period, packages without maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.

To add yourself as a bugowner of a package, please follow the steps below:
* Update to the most recent osc version (0.130) from the MeeGo tools repository. Note: this is essential, since the needed options are not released upstream yet. Tools: http://repo.meego.com/MeeGo/tools/repos/
* Identify the packages of which you are the ultimate maintainer
* Do the following for every package you maintain in the Trunk:* projects:
<code>
osc reqms --role bugowner <project> <package> -m "I want to own this because I love this package"
</code>
* Your request will be sent and someone in release engineering will approve it

The current status can be seen here: [[Packaging/Maintainers]]

== Package Naming ==
* Dash '-' must be used as the delimiter for name parts.
* Do NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.
* The spec file should be named using the %{name}.spec scheme which should also correspond to the package name within a project in the build system.

== Version and Release ==

Package Versions look like : X.Y.Z-R.B
* X.Y.Z is the 'Version' number - determined by the source package.
* R is the 'Release' number which is automatically incremented by OBS whenever a source/packaging changes (eg a check-in or request acceptance)
* B is the build number which is incremented when the package is rebuilt due to a dependency change.

=== Version ===

The Version field in the spec file is where you should put the current version of the software being packaged.
There are four cases where the version contains non-numeric characters:

* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc... Details can be found below: Non-Numeric Version.
* Post-release packages: Packages released after a "final" version. These packages contain the same numeric version as the "final" version, but have an additional non-numeric identifier. This mechanism may also be used for packaging only changes to an upstream package.
* Snapshot packages: Packages built from SCM snapshots. These packages could be either "pre" or "post" release packages.

==== Non-Numeric Version ====

We can use letters and tilde into the version tag. We do not use the Release field for this.

Example:
<pre>
Let's assume the following Qt versions:
Qt 4.7.0~beta1
Qt 4.7.0~beta1+git1
Qt 4.7.0~beta2
Qt 4.7.0

Version comparison results:
$ rpmdev-vercmp 4.7.0~beta1 4.7.0~beta1+git1
0:4.7.0~beta1+git1-None is newer

$ rpmdev-vercmp 4.7.0~beta1+git2 4.7.0~beta2
0:4.7.0~beta2-None is newer

$ rpmdev-vercmp 4.7.0~beta2 4.7.0
0:4.7.0-None is newer

Conclusion:
4.7.0~beta1 < 4.7.0~beta1+git1 < 4.7.0~beta2 < 4.7.0
</pre>

Note that the ~ comparison order is specific to MeeGo rpm (http://rpm.org/ticket/56).

=== Release ===

This field is handled by the build system to be able to manage automated builds. The initial setting in the spec file is used by the build system but in many cases it does not need to be changed.

There is no need for the %{dist} macro in the release field. This is also handled directly by the build system.

The release number is set to zero with any version update. It is increased by one with any change in the package.

We can put letters into the version tag, so we do not use the Release field for this. Details can be found above.

If you build the package outside of the OBS or if you copy a package then you will of course not get the correct Release or Build values.

== Tags ==
*The ''Packager'' tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the ''Packager'' tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the '''Maximum RPM definition of the Packager tag''' at [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG www.rpm.org] . If you need to include information about the packager in the rpms ''you'' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.
*The ''Vendor'' tag should not be used. It is set automatically by the build system.

*Usually, the ''Pre<code></code>Req'' tag should be replaced by plain ''Requires''. For more info, see Maximum RPM snapshot's [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED fine grained dependencies chapter] .
* The ''Source'' tag documents where to find the upstream sources for the rpm. In most cases this should be a complete URL to the upstream tarball.
=== Summary Tag ===
The summary is a single line string describing the package. The maximum length is 80 characters. It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.

It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.

The RPM spec file contains only the English version to keep the RPM database small.

*The ''Summary'' tag value should not end in a period. If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.

=== Group Tag ===

Valid RPM Groups are:
<pre>
Amusements/Games
Amusements/Graphics
Applications/Archiving
Applications/Communications
Applications/Databases
Applications/Editors
Applications/Emulators
Applications/Engineering
Applications/File
Applications/Internet
Applications/Multimedia
Applications/Productivity
Applications/Publishing
Applications/System
Applications/Text
Development/Debuggers
Development/Languages
Development/Libraries
Development/System
Development/Tools
Documentation
System/Boot
System/Console
System/I18n/Chinese
System/I18n/Japanese
System/I18n/Korean
System/Packages
System/Base
System/Daemons
System/Kernel
System/Libraries
System/Shells
System/X11
System/X11/Fonts
System/X11/Icons
System/GUI/XFCE
System/GUI/Other
System/GUI/GNOME
</pre>

==== Domain/Subsystem based RPM Groups ====

Following the new architecture and the new [http://meego.com/developers/meego-architecture/meego-architecture-domain-view domain view], RPM groups (The Group tag in the RPM) for core packages will be changed to match the domains and any package in the core that is part of one of the domain will have a corresponding group that matches the architecture.

{|
! Domain
! Subsystem
!Groupname
|-
| Communications || Cellular Adaptation || Communications/Cellular Adaptation
|-
| Communications || Cellular Framework || Communications/Cellular Framework
|-
| Communications || Telephony and IM || Communications/Telephony and IM
|-
| Communications || Bluetooth || Communications/Bluetooth
|-
| Communications || Connectivity Adaptation || Communications/Connectivity Adaptation
|-
| Communications || ConnMan || Communications/ConnMan
|-
| Data Management || Content Framework || Data Management/Content Framework
|-
| Development Platform || Platform SDK || Development Platform/Platform SDK
|-
| Essentials || Base Essentials || Essentials/Base Essentials
|-
| Graphics || Font Management || Graphics/Font Management
|-
| Graphics || Display and Graphics Adaptation || Graphics/Display and Graphics Adaptation
|-
| Graphics || Input Adaptation || Graphics/Input Adaptation
|-
| Graphics || Open GL ES || Graphics/Open GL ES
|-
| Graphics || X11 || Graphics/X11
|-
| Kernel || Linux Kernel || Kernel/Linux Kernel
|-
| Location || Location Framework || Location/Location Framework
|-
| Location || Location Adaptation || Location/Location Adaptation
|-
| Multimedia || Audio Adaptation || Multimedia/Audio Adaptation
|-
| Multimedia || Camera Adaptation || Multimedia/Camera Adaptation
|-
| Multimedia || Gstreamer || Multimedia/Gstreamer
|-
| Multimedia || Imaging and Video Adaptation || Multimedia/Imaging and Video Adaptation
|-
| Multimedia || Imaging Codecs || Multimedia/Imaging Codecs
|-
| Multimedia || PulseAudio || Multimedia/PulseAudio
|-
| Multimedia || Sharing || Multimedia/Sharing
|-
| Multimedia || UPnP || Multimedia/UPnP
|-
| Personal Information Management || Backup Framework || Personal Information Management/Backup Framework
|-
| Personal Information Management || Calendar Engine || Personal Information Management/Calendar Engine
|-
| Personal Information Management || Contacts Engine || Personal Information Management/Contacts Engine
|-
| Personal Information Management || Email Engine || Personal Information Management/Email Engine
|-
| Personal Information Management || Synchronization Framework || Personal Information Management/Synchronization Framework
|-
| Qt || Qt || Qt/Qt
|-
| Qt || Qt Mobility || Qt/Qt Mobility
|-
| Qt || Qt WebKit || Qt/Qt WebKit
|-
| Security || Accounts || Security/Accounts
|-
| Security || Certificate Manager || Security/Certificate Manager
|-
| Security || Integrity Protection Framework || Security/Integrity Protection Framework
|-
| Security || Access Control Framework || Security/Access Control Framework
|-
| Security || Single Sign-On || Security/Single Sign-On
|-
| Security || SW Distribution Security || Security/SW Distribution Security
|-
| Security || Security Adaptation || Security/Security Adaptation
|-
| Software Management || Package Manager || Software Management/Package Manager
|-
| System || Context Framework || System/Context Framework
|-
| System || NGF || System/NGF
|-
| System || Resource Policy || System/Resource Policy
|-
| System || Sensor Adaptation || System/Sensor Adaptation
|-
| System || Sensor Framework || System/Sensor Framework
|-
| System || Startup Services || System/Startup Services
|-
| System || System Control || System/System Control
|-
| System || Device Mode Adaptation || System/Device Mode Adaptation
|-
| System || Vibra and Haptics Adaptation || System/Vibra and Haptics Adaptation
|-

|}

=== BuildRoot tag ===
The ''BuildRoot'' value MUST be below <code>%{_tmppath}/</code> and MUST contain at least <code>%{name}</code>, <code>%{version}</code> and <code>%{release}</code>.

The ''recommended'' values for the ''BuildRoot'' tag are (in descending order of preference) :
<pre>
%{_tmppath}/%{name}-%{version}-%{release}-root
</pre>

The BuildRoot tag can be omitted in packages targeting MeeGo only and is handled directly by rpm in MeeGo, for packages that need to run on other distros with older rpm it should be added for backward compatibility.

=== PreReq ===

Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.

=== Explicit Requires ===
Packages must not contain explicit ''Requires'' on libraries except when absolutely
necessary. When explicit library ''Requires'' are necessary, there should be a spec file comment justifying it.

We generally rely on rpmbuild to automatically add dependencies on library SONAMEs.
Modern package management tools are capable of resolving such dependencies to determine
the required packages. Explicit dependencies on specific package names may aid the
inexperienced user, who attempts at installing RPM packages manually, however, history
has shown that such dependencies add confusion when library/files are moved from one
package to another, when packages get renamed, when one out of multiple alternative
packages would suffice, and when versioned explicit dependencies become out-of-date and
inaccurate. Additionally, in some cases, old explicit dependencies on package names
require unnecessary updates/rebuilds.

Exemplary rationale for a versioned explicit dependency:
<pre>
# The automatic dependency on libfubar.so.1 is insufficient,
# as we strictly need at least the release that fixes two segfaults.
Requires: libfubar >= 0:1.2.3-7
</pre>

Packagers should revisit an explicit dependency as appropriate to avoid
it becoming inaccurate and superfluous.

=== BuildRequires ===

In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds with that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.

Before adding Build<code></code>Requires to any package, please be comfortable with [[#Requires| Requires]] .

=== Patches ===
Each problem should be solved in a separate patch. To allow easy maintenance of patches, every patch should have a header providing the following information:

* Authors' names
* [http://meego.com/about/contribution-guidelines/signed-process Signed-off-by] tag
* Detailed description of the fixed problem
* URL of the original source of the patch if any

The name of a patch file consists of:

* The name and version of the source tarball from which the patched file is derived
* Some words that characterize the patch content
* The filename suffix <code class="filename">.patch</code>

Patches are in the unified format ('''diff -u''') and should be applied with 1 strip level in the spec file ('''%patch -p1'''). The only exceptions are the patches obtained from an another primary source site. The original name, suffix, and format is preserved in this case.

Each patch should be compressed with '''bzip2''' if its size is greater than 100kB. The macros <code class="systemitem">%name</code> and <code class="systemitem">%version</code> should be used whenever possible.

Example:

Source: %{name}-%{version}.tar.bz2
Patch0: %{name}-%{version}-autoconf.patch
Patch1: %{name}-%{version}-gcc31.patch

For the patches to be applied, the patches should be mentioned under %setup. For the above example, this could be done as

%setup -q
%patch0 -p1
%patch1 -p1

Patches have to be marked as such in the spec file and should be applied using the internal patch routines available in rpm. Use of alternate patch management system not supported by rpm is not allowed.

=== %clean ===

The %clean section is not required for MeeGo 1.1 and above. Each package for MeeGo 1.0 MUST have a %clean section, which contains rm -rf %{buildroot} (or $RPM_BUILD_ROOT).

== Documentation ==
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention about which subpackage you include documentation in, for example API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.

Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.

== Devel Packages ==
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:
* Header files (such as .h files)
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.

A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.

=== Requiring Base Package ===
Devel packages must require the base package using a fully versioned dependency: <code>Requires: %{name} = %{version}-%{release}</code>.
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.

=== Pkgconfig Files ===
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.

== Test Packages ==
Tests should be included in -test subpackage or separate package according to the following guidelines.

[http://wiki.meego.com/Test_Packaging Test Packaging Guidelines]

== Shared Libraries ==
Whenever possible (and feasible), MeeGo Packages containing libraries should build them as shared libraries. In addition, every binary RPM package which contains shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in <code>%post</code> and <code>%postun</code>. If the package has multiple subpackages with libraries, each subpackage should also have a <code>%post/%postun</code> section that calls <code>/sbin/ldconfig</code>. An example of the correct syntax for this is:
<pre>
%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig
</pre>
Note that this specific syntax only works if <code>/sbin/ldconfig</code> is the only call in <code>%post</code> and <code>%postun</code>. If you have additional commands to run during the scriptlet, call <code>/sbin/ldconfig</code> at the beginning of the scriptlet, like this:
<pre>
%post
/sbin/ldconfig
/usr/bin/foo --add

%postun
/sbin/ldconfig
/usr/bin/foo --remove
</pre>

== Configuration files ==

Configuration files must be marked as such in packages.

As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.

Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in MeeGo.

== Initscripts ==

Currently, only SystemV-style initscripts are supported in MeeGo.

== Desktop files ==

If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]
entries.

=== Icon tag in Desktop Files ===
The icon tag can be specified in two ways:

* Full path to specific icon file:
<code> Icon=/usr/share/pixmaps/comical.png </code>

* Short name without file extension:
<code> Icon=comical </code>

The short name without file extension is preferred, because it allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm), but either method is acceptable.

=== .desktop file creation ===
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by including a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file. Here are the contents of a sample .desktop file (comical.desktop):

<pre>
[Desktop Entry]
Name=Comical
GenericName=Comic Archive Reader
Comment=Open .cbr & .cbz files
Exec=comical
Icon=comical
Terminal=false
Type=Application
Categories=Graphics;
</pre>

=== Localizing .desktop files ===
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' locale codes are needed. For example:

<pre>
[Desktop Entry]
Type=Application
Name=Clocks
Name[de]=Uhrzeit
Name[es]=Relojes
Name[fr]=Horloges
Name[pt_BR]=Relógios
Name[zh_CN]=时钟
Icon=meego-app-clocks
Exec=meego-qml-launcher --opengl --fullscreen --app meego-app-clocks
</pre>

=== desktop-file-install usage ===
It is not simply enough to just include the .desktop file in the package, one MUST run <code>desktop-file-install</code> OR <code>desktop-file-validate</code> in <code>%install</code> (and have <code>BuildRequires: desktop-file-utils</code>), to help ensure .desktop file safety and spec-compliance. <code>desktop-file-install</code> MUST be used if the package does not install the file or there are changes desired to the .desktop file (such as add/removing categories, etc). <code>desktop-file-validate</code> MAY be used instead if the .desktop file's content/location does not need modification. Here are some examples of
usage:

<pre>
desktop-file-install \
--dir=${RPM_BUILD_ROOT}%{_datadir}/applications \
%{SOURCE3}
</pre>

<pre>
desktop-file-install \
--add-category="AudioVideo" \
--delete-original \
--dir=%{buildroot}%{_datadir}/applications \
%{buildroot}/%{_datadir}/foo.desktop
</pre>

<pre>
desktop-file-validate %{buildroot}/%{_datadir}/applications/foo.desktop
</pre>

== Macros ==
=== Using %{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS ===
There are two styles of defining the rpm Build Root and Optimization Flags in a spec file:

{| border="1"
|-
| ||macro style || variable style
|-
|Build Root||%{buildroot}||$RPM_BUILD_ROOT
|-
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS
|}

There is very little value in choosing one style over the other, since they will resolve to the same values in all scenarios. You should pick a style and use it consistently throughout your packaging.

Mixing the two styles, while valid, is bad from a QA and usability point of view, and should not be done in MeeGo packages.

== Handling Locale Files ==

If the package includes translations, add
<pre>
BuildRequires: gettext
</pre>
If you don't, your package could fail to generate translation files in the buildroot.

MeeGo includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:
<pre>
%find_lang %{name}
</pre>
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.
<pre>
%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/foobar
...
</pre>
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)

Here is an example of proper usage of <code>%find_lang</code>, in <code>foo.spec</code>:

<pre>
...
%prep
%setup -q

%build
%configure --with-cheese
make %{?_smp_mflags}

%install
make DESTDIR=%{buildroot} install
%find_lang %{name}

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc LICENSE README
%{_bindir}/foobar

</pre>

=== Why do we need to use %find_lang? ===

Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.

* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:
<pre>
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo
...
</pre>
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.

Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.

== Scriptlets ==
Great care should be taken when using scriptlets in MeeGo packages. If scriptlets are used, those scriptlets must be sane.

=== Scriptlets requirements ===
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:
<pre>
Requires(pre): ...
Requires(post): ...
</pre>
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .

=== Running scriptlets only in certain situations ===
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:
<pre>
install erase upgrade reinstall
%pre 1 - 2 2
%post 1 - 2 2
%preun - 0 1 -
%postun - 0 1 -
</pre>
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:
<pre>
%preun
if [ $1 -eq 0 ] ; then
/sbin/chkconfig --del %{name}
fi
</pre>
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.

=== Scriplets are only allowed to write in certain directories ===
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix

{| border="1"
|-
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}
|-
|%prep || yes || yes || no
|-
|%build || yes || yes || no
|-
|%install || yes || yes || yes
|-
|%check || yes || yes || no
|-
|%clean || yes || yes || yes
|}

Further clarification: That should hold true irrespective of the builder's uid.

== Use of Epochs ==
The Epoch tag in RPM is to be used only as a last resort, and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease transition from third party repositories.

== Writing a package from scratch ==

See [[Spectacle]]

Spectacle is a great tool for straightforward packages, and we have many of those, hundreds, many of those packages already have been using spectacle happily for a while now. Generally, the 80/20 rule applies here, almost 80% of packages in MeeGo can be converted to this format, probably around 20% will need to stay as is for various reasons.

Spectacle in general helps a lot when you have a package that does:
* configure
* make
* make install

and especially useful when for example you have to manage many build dependencies and patches or for common packaging of perl/python/X packages that usually follows the same packaging work flow. We have plans to add lots of nice features to make packaging easier and more fun with spectacle.

While spectacle has many advanced options to cover all kind of corner cases, it should not be used for complex packages that would require lots of customization, especially now that we support multiple architectures and where we need to apply code and custom scripts to support different scenarios.

Spectacle provides scripts to convert spec files to spectacle, those try to do their best but you SHOULD never just take the output as is and rely on the script, a review of the output is necessary, otherwise you might end up with lots of duplication in the spec file. This is the most common mistake, developers are relying on the output of the conversion script, basically picking some spec file from another distro and converting it. This can lead to major disasters in some cases.

So to summarize:
* It is NOT mandatory to use spectacle
* If you try to convert and find yourself spending more than a few minutes on a package, then probably there is something wrong and you should not be using that or you should RTFM.
* Use it with care, especially when you first import the data from existing spec files or when you first create your YAML file
* Your distro maintainer might send you a note that certain packages you are maintaining could be converted to spectacle easily, but she/he should not reject your package because it does not use spectacle.
* If you find yourself forced to edit the spec file manually for some reason, then either:
** your package is not suitable to be used with spectacle
** or you might want to ask for a feature to support that special case
* packager should not change packaging format randomly.
** You need to be the main maintainer
** If a package is already using the yaml format, you need to have a valid reason why not to use the yaml format

== Modifying existing Packages ==

If you base a new package on an existing non-MeeGo package, make sure you verify its correctness of the package and the spec file and to understand exactly what has been done to package the software exactly. Do not submit a package without knowing what those strange, but innocent-looking commands do.

In particular, you should

* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory
* verify any sources and patches and remove patches or sources that:
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)
** Implement features we do not support (example: selinux)
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.
* verify that the license stated in the spec file matches the actual license of the software,
* skim the summary and description for typos and oddities (see Summary and description ),
* make sure that the correct build root is used,
* ensure that macro usage is consistent and that the macros are available in MeeGo (see Macros ).

Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.

== Changelogs ==

This section describes the MeeGo policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.)

Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent.

Please bear in mind theat MeeGo changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.

=== General information ===

* MeeGo uses a separate file for package changes which is similar to a debian changelog file. This file is named as the spec file, but ends in *.changes instead of *.spec
* Entries in the changes file should have the following structure:
<pre>
* dow mmm dd yyyy Name Goes Here <your@email.com> - [version]
- comment
- comment

</pre>

Note the following exceptions are noted through observation:
* version is often omitted (such as: alsa-utils 1.0.15-1 -> 1.0.16-1)
* there are multiple changelog entries per version (such as: alsa-utils 1.0.19)
* the hyphen between email and version is often omitted (such as: alsa-utils)
* spaces between name and <email> are omitted (such as: Zhang, Qiang Z<qiang.z.zhang@intel.com> nano)
* name is sometimes omitted (such as: bitstream-vera-fonts nicolas.mailhot at laposte.net)
* <email> is sometimes omitted (such as: binutils Jim Kingdon)
This wide variation in formats makes automation tasks harder than they should be. Please use the correct format.

=== External References ===

Each external reference (bug numbers etc) should be of the form:
"(" + external reference code + bug number +")"

Currently defined:
* MeeGo Bugs : BMC#
* MeeGo Features: FEA#
* Common Vulnerability / Exposure : CVE

==== Bug Numbers in the change log ====

During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be an number from https://bugzilla.meego.com/. Add an entry with bugzilla number and a short description of the bug-summary. For example:
- Removed invalid desktop Category "Application" (BMC#4654).
- Symlink icon to pixmaps dir (BMC#2108)
- Added gnome-ui-properties to control-center (BMC#1960).

New packages related to new features will refer to the corresponding bug number in bugzilla, preceded with an FEA. For example:
- Adding Qt Contacts support FEA#8011

==== CVE numbers in change log ====

As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry. Examples:
- Add gdk-pixbuf-226710.patch (BMC#226710), and (CVE-2007-0010).
- More XPM fixes: (CVE-2005-2975) xpm too many colors DoS (BMC#129642)
- fix ~/.dmrc symlink attack (BMC#180704), (CVE-2006-2449)

=== Spec File changes ===
Be as precise as possible! This is especially important if you remove something from the spec file.

* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.
* Extra commands (for example during %install) can be illustrated with a short comment in spec file
* Adding/Removing packages from Requires/Provides must be described in the changelog

=== Source Code changes ===

Document the most important changes but limit verbosity.

* look into the source changelog and pick up the most important changes for the distribution (changes for other operation systems are not important). What has changed in the new version, usually in the level of detail of a NEWS file, the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.
* arrange the original changes behind the version update information. Example:
- Update to 1.3.2:
+ fixes memory leak in import function
+ new API command: unlock_client()
+ the following bugs are closed by this new upstream release:
++ ............ [MGN:332]
++ .............[MGN:337]
- split of devel package
* If upstream does not provide a meaningful change log, then only do best effort. Don't waste too much time over it.
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consists of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).

== Packaging Static Libraries ==
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries not static versions.

Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.

=== Packaging Static Libraries ===
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.

* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage. When doing this you also must have a virtual Provide for the ''*-static'' package:
<pre>%package devel
Provides: foo-static = %{version}-%{release}</pre>

Packages which explicitly need to link against the static version must <code>BuildRequire: foo-static</code>, so that the usage can be tracked.

* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage. The devel subpackage must have a virtual Provide for the ''*-static'' package, and packages dependent on it must <code>BuildRequire</code> the ''*-static'' package.

=== Staticly Linking Executables ===
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.

[[Category:Packaging]]

User:Pmccarty

2011-04-28T18:02:41Z

Pmccarty: typo fix

'''Patrick McCarty'''

I am a software engineer working for Intel.

IRC nick on freenode: pmccarty

User:Pmccarty

2011-04-28T18:01:56Z

Pmccarty: reorganization

'''Patrick McCarty'''

I am a software engineer working for Intel.

#freenode IRC nick: pmccarty

Architecture/planning/evolution-data-server

2011-04-28T17:57:47Z

Pmccarty: /* Contact Storage */

== Introduction ==

The architecture decision to make the transition from Nokia-supported components for contacts and calendar data (PIM) storage, email storage and transports, and sync back to the components used in MeeGo Netbook (Evolution Data Server and SyncEvolution) [http://lists.meego.com/pipermail/meego-dev/2011-March/481890.html was announced publicly] on March 7th. Planning the execution of that change is currently (end of March 2011) in progress.

This page gathers information about the PIM + mail storages and sync. Main author and point of contact is [mailto:patrick.ohly@intel.com Patrick Ohly]. It includes information contributed by various people, mentioned with email address below.

Information that has not been confirmed is marked with a question mark.

[[File:Qtcontacts-kcal-eds.png]]

== Calendar Storage ==

'''Maemo solution''': QtMobility/QtOrganizer (API) + KCalCore (MeeGo) + modifications + mKCal (sqlite storage) 
'''EDS proposal''': QtMobility/QtOrganizer (API) + KCalCore (KDE-compatible) + [[/KCal-EDS/]] + libecal/libical (client side) + EDS (server side, stored in iCalendar 2.0 text file) 
'''Used by''': calendar app ([mailto:sirisha.muppavarapu@intel.com Sirisha Muppavarapu]), clock app (originally [mailto:todd.e.brandt@intel.com Todd Brandt])

'''Advantages of mKCal''':
* partial loading of data from sqlite (not used by calendar app); EDS holds complete calendar in memory
* incremental changes to database; EDS must rewrite complete file
'''Disadvantages of mKCal (current implementation)''':
* only provides single "database changed" signal, forces apps to reload everything (not currently done in calendar app); EDS sends add/update/delete notifications to apps watching a calendar

Plan:
* use upstream KDE version of KCalCore (current MeeGo version has semantic differences in event->dtEnd()), with those changes that are necessary to run in MeeGo (embedded KDateTime, timed integration)
* write [[/KCal-EDS|storage which uses libecal/EDS]]
* [[/eds-improvements|EDS improvements]]

== Contact Storage ==

'''Maemo solution''': QtContacts (API) + QtContacts-Tracker (glue code) + Tracker (storage) + contactsd (updating presence information in Tracker) 
'''EDS proposal''': QtContacts (API) + [[/QtContacts storage plugin|QtContacts-EDS]] + libebook (client side) + EDS (server side, storage of vCards in Berkley DB); libfolks as replacement for contactsd 
'''Used by''': libseaside/meego-app-contacts/meego-handset-people/ContactPicker.qml ([mailto:connie.berardi@intel.com Connie Berardi] and [mailto:kaitlin.rupert@intel.com Kaitlin Rupert]), SMS and Messaging apps ([mailto:benjamin.t.drucker@intel.com Ben Drucker]), various parts of Tablet UX via QML binding, obexd for Phone Book Access Protocol (PBAP) plugin) 

'''Advantages of Tracker''':
* supports potential future use cases (combining data from different categories, partial reading/writing, fine-grained annotations on data origin)
* better searching
* scalability (?)
* read performance (?)

'''Disadvantages of Tracker''':
* data protection missing in both EDS and Tracker, but less obvious how to implement it in Tracker
* slow write performance in QtContacts-Tracker (?)

'''Plan''':
* write a QtContacts storage plugin ([[/QtContacts storage plugin|details on QtContacts-EDS]]),
* [[/eds-improvements|EDS improvements]]
* libfolks provides a QtContacts API (in addition to native APIs) and can use either Tracker or EDS directly as backends. Additional work will be needed to improve the EDS part and performance/memory usage.

'''Opens''':
* obexd has PBAP plugin for EDS, needs to be tested/improved/adapted (photo support, vCard 2.1/3.0); can't use QtContacts-EDS because obexd accesses Tracker directly
* [http://lists.meego.com/pipermail/meego-dev/2011-March/482065.html communication history], currently done with QSettings in dialer app - how will that be done in the future?

== Mail Storage and Transports ==

'''Maemo solution''': QtMobility/QtMessaging (API) + Qt Messaging Framework (QMF, actual implementation) 
'''EDS proposal''': QtMobility/QtMessaging (API) + QMF-compatible API (?) + Camel library (part of EDS, but not running in the daemon itself yet) 
'''Used by''': mail app ([mailto:carl.wong@intel.com Carl Wong]), SMS storage plugin ([mailto:benjamin.t.drucker@intel.com Ben Drucker])

'''Advantages of QMF''':
* already works as a stand-alone daemon

'''Plan A [[/email-design|(details)]]'''
* kudos to [mailto:srinivasa.ragavan.venkateswaran@intel.com Srinivasa (Srini) Venkateswaran] for this proposal
* write simplistic server which runs Camel
* replace QMF client library with one which accesses that server - ideally this library is at least QMF API source code compatible (=> adapting apps and QtMobility/QtMessaging requires recompilation, not rewriting)
* account setup UI

Some possible variations of plan A:
* rewrite mail app and QtMobility/QtMessaging to use Camel daemon via D-Bus
* QMF (source code) compatible replacement, used by mail app and Messaging (proposal above)
* rewrite mail app to use Messaging, rewrite Messaging to use Camel via D-Bus

'''Plan B''':
* keep QMF as mail infrastructure

== Data Synchronization ==
'''Maemo solution''': Buteo Sync Framework, Buteo SyncML, Buteo Sync Plugins, Buteo Media Transfer Protocol (MTP) 
'''Alternative''': SyncEvolution, Synthesis SyncML, Buteo Media Transfer Protocol 

'''Advantages of Buteo''':
* plugable sync engines, more sophisticated scheduling of time-based syncs
* Tablet Google Contact sync preserves properties not supported by Google

'''Disadvantages of Buteo''':
* incomplete, untested (in MeeGo)
* no support for incoming SyncML over OBEX/Bluetooth

'''Step 1''':
* keep Buteo Sync Framework
* replace SyncML engine for Google Contact sync in Tablet with SyncEvolution + Synthesis:
** The [http://meego.gitorious.org/meego-middleware/syncevolution/blobs/master/src/backends/buteo/ButeoBridge.cpp existing Buteo sync plugin] must also [https://bugs.meego.com/show_bug.cgi?id=15031 support Google Contacts]. No support for any other SyncML peer. This is the only SyncML peer which was tested with Buteo in MeeGo (done by the Intel Tablet team), so not supporting other SyncML peers in step 1 is not a regression.
** [https://bugs.meego.com/show_bug.cgi?id=15030 Preserving local extensions] when synchronizing with Google depends on [https://bugs.meego.com/show_bug.cgi?id=15029 hard-coding capabilities of that peer] and [https://bugs.meego.com/show_bug.cgi?id=15030 support for unknown properties].
** Google Contact sync might run in parallel with CalDAV sync. The SyncEvolution sync plugin must support that. Must [https://bugs.meego.com/show_bug.cgi?id=681 replace global variables].

'''Step 2''':
* rewrite QML settings backend to use SyncEvolution D-Bus API
* remove Buteo msyncd/framework, run Buteo MTP as part of syncevo-dbus-server or stand-alone

'''Further improvements to SyncEvolution/MTP''':
* code refactoring of libsynthesis to support non-SyncML sync scenarios and plain C code which needs data conversion (obexd plugin?)
* support push sync
* redesign daemon to run syncs in forked processes (security, responsiveness of D-Bus API)
* device-to-device sync over WLAN
* MTP over WLAN and Bluetooth

Taking screenshots on MeeGo

2011-04-25T18:28:17Z

Pmccarty: /* ImageMagick */ add missing step

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* procedure for taking native screenshots under MeeGo UX. This section lists some different methods for taking screenshots until an easy solution is implemented.

=== ImageMagick ===

The following steps outline one possible command-line approach, using the <tt>import</tt> command from ImageMagick:

* Make sure your device is connected to the internet.
* Open the Terminal application. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> by running the command

<code>zypper in ImageMagick</code>

* Exit the root environment by typing <tt>exit</tt>.
* Type <tt>exit</tt> once more to close the Terminal application.
* Prepare the display for a screenshot by opening applications, performing tasks, etc. When the display is ready for a screenshot, proceed to the next step.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot. You can use the <tt>cd</tt> command to change directories.
* Run the following command:

<code>export DISPLAY=:0.0</code>

* Run the following command, where "filename.png" is the name you want for the screenshot image.

<code>import filename.png</code>

* Type Alt+F2 to return to the X session.
* Click (or touch) the display, and wait a few seconds before proceeding to the next step.
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without displaying any warnings or error messages.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-21T19:26:50Z

Pmccarty: reorganize page structure, anticipating future expansion

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* procedure for taking native screenshots under MeeGo UX. This section lists some different methods for taking screenshots until an easy solution is implemented.

=== ImageMagick ===

The following steps outline one possible command-line approach, using the <tt>import</tt> command from ImageMagick:

* Make sure your device is connected to the internet.
* Open the Terminal application. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> by running the command

<code>zypper in ImageMagick</code>

* Exit the root environment by typing <tt>exit</tt>.
* Type <tt>exit</tt> once more to close the Terminal application.
* Prepare the display for a screenshot by opening applications, performing tasks, etc. When the display is ready for a screenshot, proceed to the next step.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot. You can use the <tt>cd</tt> command to change directories.
* Execute the following command, where "filename.png" is the name you want for the screenshot image.

<code>import filename.png</code>

* Type Alt+F2 to return to the X session.
* Click (or touch) the display, and wait a few seconds before proceeding to the next step.
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without displaying any warnings or error messages.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-21T18:28:36Z

Pmccarty: /* ImageMagick method */ more clarifications

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

=== ImageMagick method ===

Currently, there is no *easy* procedure for taking native screenshots under MeeGo UX. The following steps outline a possible command-line approach, using the <tt>import</tt> command from ImageMagick:

* Make sure your device is connected to the internet.
* Open the Terminal application. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> by running the command

<code>zypper in ImageMagick</code>

* Exit the root environment by typing <tt>exit</tt>.
* Type <tt>exit</tt> once more to close the Terminal application.
* Prepare the display for a screenshot by opening applications, performing tasks, etc. When the display is ready for a screenshot, proceed to the next step.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot. You can use the <tt>cd</tt> command to change directories.
* Execute the following command, where "filename.png" is the name you want for the screenshot image.

<code>import filename.png</code>

* Type Alt+F2 to return to the X session.
* Click (or touch) the display, and wait a few seconds before proceeding to the next step.
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without displaying any warnings or error messages.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-21T18:22:03Z

Pmccarty: /* MeeGo UX */ add some more fluff to the descriptions

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

=== ImageMagick method ===

Currently, there is no *easy* procedure for taking native screenshots under MeeGo UX. The following steps outline a possible command-line approach, using the <tt>import</tt> command from ImageMagick:

* Make sure you have an active internet connection.
* Open the Terminal. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> with the command

<code>zypper in ImageMagick</code>

* Exit the root environment by typing <tt>exit</tt>.
* Type <tt>exit</tt> once more to close out of the Terminal application.
* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot image.

<code>import filename.png</code>

* Type Alt+F2 to return to the X session.
* Click (or touch) the display, and wait a few seconds before proceeding to the next step.
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without displaying any warnings or error messages.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-21T18:11:39Z

Pmccarty: clarify the instructions to make sure Terminal is closed before proceeding

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

* Make sure you have an active internet connection.
* Open the Terminal. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> with the command

<code># zypper in ImageMagick</code>

* Exit the root environment by typing <tt>exit</tt>.
* Type <tt>exit</tt> once more to close out of the Terminal application.
* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot.

<code>$ import filename.png</code>

* Return to the X session by typing Alt+F2
* Click (or touch) the display and wait a few seconds
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
* That's it! Your screenshot can be found in the current directory.

Packaging/Maintainers

2011-04-20T19:09:03Z

Pmccarty: add the devel project as well

{|border="1"
! Package
! Maintainers (bugowner)
! Development Project
|-

|[http://build.meego.com/package/show?package=ConsoleKit&project=Trunk ConsoleKit]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=FUR&project=Trunk FUR]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=GConf-dbus&project=Trunk GConf-dbus]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=ImageMagick&project=Trunk ImageMagick]
|
|
|-
|[http://build.meego.com/package/show?package=MAKEDEV&project=Trunk MAKEDEV]
|
|
|-
|[http://build.meego.com/package/show?package=ORBit2&project=Trunk ORBit2]
|
|
|-
|[http://build.meego.com/package/show?package=OpenCV&project=Trunk OpenCV]
|
|
|-
|[http://build.meego.com/package/show?package=OpenEXR&project=Trunk OpenEXR]
|
|
|-
|[http://build.meego.com/package/show?package=PackageKit&project=Trunk PackageKit]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=PyOpenGL&project=Trunk PyOpenGL]
|
|
|-
|[http://build.meego.com/package/show?package=PyXML&project=Trunk PyXML]
|
|
|-
|[http://build.meego.com/package/show?package=PyYAML&project=Trunk PyYAML]
|jfding
|
|-
|[http://build.meego.com/package/show?package=SDL&project=Trunk SDL]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_Pango&project=Trunk SDL_Pango]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_gfx&project=Trunk SDL_gfx]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_image&project=Trunk SDL_image]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_mixer&project=Trunk SDL_mixer]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_net&project=Trunk SDL_net]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_ttf&project=Trunk SDL_ttf]
|
|
|-
|[http://build.meego.com/package/show?package=SOAPpy&project=Trunk SOAPpy]
|
|
|-
|[http://build.meego.com/package/show?package=WebKit&project=Trunk WebKit]
|yanli
|
|-
|[http://build.meego.com/package/show?package=WiMAX-Network-Service&project=Trunk WiMAX-Network-Service]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=Xaw3d&project=Trunk Xaw3d]
|
|
|-
|[http://build.meego.com/package/show?package=abiword&project=Trunk abiword]
|
|
|-
|[http://build.meego.com/package/show?package=acct&project=Trunk acct]
|
|
|-
|[http://build.meego.com/package/show?package=acl&project=Trunk acl]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=acpid&project=Trunk acpid]
|
|
|-
|[http://build.meego.com/package/show?package=adns&project=Trunk adns]
|
|
|-
|[http://build.meego.com/package/show?package=aiksaurus&project=Trunk aiksaurus]
|
|
|-
|[http://build.meego.com/package/show?package=alsa-lib&project=Trunk alsa-lib]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=alsa-plugins&project=Trunk alsa-plugins]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=alsa-utils&project=Trunk alsa-utils]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=anerley&project=Trunk anerley]
|rbradford
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=anjuta&project=Trunk anjuta]
|
|
|-
|[http://build.meego.com/package/show?package=anthy&project=Trunk anthy]
|
|
|-
|[http://build.meego.com/package/show?package=apr&project=Trunk apr]
|
|
|-
|[http://build.meego.com/package/show?package=apr-util&project=Trunk apr-util]
|
|
|-
|[http://build.meego.com/package/show?package=aria2&project=Trunk aria2]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=asciidoc&project=Trunk asciidoc]
|
|
|-
|[http://build.meego.com/package/show?package=asio&project=Trunk asio]
|
|
|-
|[http://build.meego.com/package/show?package=aspell&project=Trunk aspell]
|
|
|-
|[http://build.meego.com/package/show?package=aspell-en&project=Trunk aspell-en]
|
|
|-
|[http://build.meego.com/package/show?package=at&project=Trunk at]
|
|
|-
|[http://build.meego.com/package/show?package=at-spi&project=Trunk at-spi]
|
|
|-
|[http://build.meego.com/package/show?package=atk&project=Trunk atk]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=atproxy&project=Trunk atproxy]
|jpfreyen,ulf
|
|-
|[http://build.meego.com/package/show?package=attica&project=Trunk attica]
|boudra
|
|-
|[http://build.meego.com/package/show?package=attr&project=Trunk attr]
|
|
|-
|[http://build.meego.com/package/show?package=audio_management&project=Trunk audio_management]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=audiofile&project=Trunk audiofile]
|
|
|-
|[http://build.meego.com/package/show?package=augeas&project=Trunk augeas]
|
|
|-
|[http://build.meego.com/package/show?package=autoconf&project=Trunk autoconf]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=autoconf213&project=Trunk autoconf213]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=autogen&project=Trunk autogen]
|
|
|-
|[http://build.meego.com/package/show?package=automake&project=Trunk automake]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automake14&project=Trunk automake14]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automake17&project=Trunk automake17]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automoc4&project=Trunk automoc4]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=autotrace&project=Trunk autotrace]
|
|
|-
|[http://build.meego.com/package/show?package=avahi&project=Trunk avahi]
|
|
|-
|[http://build.meego.com/package/show?package=babl&project=Trunk babl]
|
|
|-
|[http://build.meego.com/package/show?package=baekmuk-ttf-fonts&project=Trunk baekmuk-ttf-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=banshee-1&project=Trunk banshee-1]
|abock
|
|-
|[http://build.meego.com/package/show?package=banshee-1-branding-meego&project=Trunk banshee-1-branding-meego]
|
|
|-
|[http://build.meego.com/package/show?package=basesystem&project=Trunk basesystem]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bash&project=Trunk bash]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=bash-x86&project=Trunk bash-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=bc&project=Trunk bc]
|
|
|-
|[http://build.meego.com/package/show?package=bind&project=Trunk bind]
|jfding
|
|-
|[http://build.meego.com/package/show?package=binutils&project=Trunk binutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bisho&project=Trunk bisho]
|ross
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=bison&project=Trunk bison]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bitmap&project=Trunk bitmap]
|
|
|-
|[http://build.meego.com/package/show?package=bitstream-vera-fonts&project=Trunk bitstream-vera-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=bluetooth-ivi&project=Trunk bluetooth-ivi]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=bluez&project=Trunk bluez]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=boardname&project=Trunk boardname]
|auke
|
|-
|[http://build.meego.com/package/show?package=bognor-regis&project=Trunk bognor-regis]
|
|
|-
|[http://build.meego.com/package/show?package=boost&project=Trunk boost]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=bootchart&project=Trunk bootchart]
|auke
|
|-
|[http://build.meego.com/package/show?package=bootstub&project=Trunk bootstub]
|praj
|
|-
|[http://build.meego.com/package/show?package=booty&project=Trunk booty]
|
|
|-
|[http://build.meego.com/package/show?package=brasero&project=Trunk brasero]
|
|
|-
|[http://build.meego.com/package/show?package=btrfs-progs&project=Trunk btrfs-progs]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=bugle&project=Trunk bugle]
|
|
|-
|[http://build.meego.com/package/show?package=build&project=Trunk build]
|nashif
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=build-compare&project=Trunk build-compare]
|nashif
|
|-
|[http://build.meego.com/package/show?package=busybox&project=Trunk busybox]
|
|
|-
|[http://build.meego.com/package/show?package=buteo-mtp&project=Trunk buteo-mtp]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-sync-plugins&project=Trunk buteo-sync-plugins]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-syncfw&project=Trunk buteo-syncfw]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-syncml&project=Trunk buteo-syncml]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=byacc&project=Trunk byacc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bzip2&project=Trunk bzip2]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=bzip2-libs-x86&project=Trunk bzip2-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=bzip2-x86&project=Trunk bzip2-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=c-ares&project=Trunk c-ares]
|
|
|-
|[http://build.meego.com/package/show?package=ca-certificates&project=Trunk ca-certificates]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=cabextract&project=Trunk cabextract]
|
|
|-
|[http://build.meego.com/package/show?package=cairo&project=Trunk cairo]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=cairomm&project=Trunk cairomm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=calligra&project=Trunk calligra]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=camera-adaption-layer&project=Trunk camera-adaption-layer]
|ulf
|
|-
|[http://build.meego.com/package/show?package=catdoc&project=Trunk catdoc]
|
|
|-
|[http://build.meego.com/package/show?package=ccache&project=Trunk ccache]
|nashif
|
|-
|[http://build.meego.com/package/show?package=cdrdao&project=Trunk cdrdao]
|
|
|-
|[http://build.meego.com/package/show?package=cdrkit&project=Trunk cdrkit]
|
|
|-
|[http://build.meego.com/package/show?package=cedevicemanager&project=Trunk cedevicemanager]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=cglaunch&project=Trunk cglaunch]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=check&project=Trunk check]
|
|
|-
|[http://build.meego.com/package/show?package=cheese&project=Trunk cheese]
|
|
|-
|[http://build.meego.com/package/show?package=chkconfig&project=Trunk chkconfig]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=chrome-meego-extension&project=Trunk chrome-meego-extension]
|nhu
|
|-
|[http://build.meego.com/package/show?package=chromium&project=Trunk chromium]
|
|devel:browser
|-
|[http://build.meego.com/package/show?package=chrpath&project=Trunk chrpath]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=cjkuni-fonts&project=Trunk cjkuni-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=clean-device&project=Trunk clean-device]
|kedz
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=cloog&project=Trunk cloog]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=clucene&project=Trunk clucene]
|boudra
|
|-
|[http://build.meego.com/package/show?package=clutter&project=Trunk clutter]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-box2d&project=Trunk clutter-box2d]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-gesture&project=Trunk clutter-gesture]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-gst&project=Trunk clutter-gst]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-gtk&project=Trunk clutter-gtk]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-imcontext&project=Trunk clutter-imcontext]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=cmake&project=Trunk cmake]
|austin,boudra
|
|-
|[http://build.meego.com/package/show?package=cmake-gui&project=Trunk cmake-gui]
|boudra
|
|-
|[http://build.meego.com/package/show?package=commhistory-daemon&project=Trunk commhistory-daemon]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=compat-libstdc++-33&project=Trunk compat-libstdc++-33]
|austin
|
|-
|[http://build.meego.com/package/show?package=compat-telepathy-qt4&project=Trunk compat-telepathy-qt4]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=compface&project=Trunk compface]
|
|
|-
|[http://build.meego.com/package/show?package=comps-extras&project=Trunk comps-extras]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=connman&project=Trunk connman]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=connman-qt&project=Trunk connman-qt]
|kevronx_m_rees
|
|-
|[http://build.meego.com/package/show?package=contacts&project=Trunk contacts]
|
|
|-
|[http://build.meego.com/package/show?package=contactsd&project=Trunk contactsd]
|
|devel:people
|-
|[http://build.meego.com/package/show?package=contextkit&project=Trunk contextkit]
|rusty,lamadon
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=contextkit-maemo&project=Trunk contextkit-maemo]
|rusty,lamadon
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=contextkit-meego&project=Trunk contextkit-meego]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=coreutils&project=Trunk coreutils]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=coreutils-x86&project=Trunk coreutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=corewatcher&project=Trunk corewatcher]
|wdouglas
|
|-
|[http://build.meego.com/package/show?package=corkscrew&project=Trunk corkscrew]
|boudra
|
|-
|[http://build.meego.com/package/show?package=cpio&project=Trunk cpio]
|yanli
|
|-
|[http://build.meego.com/package/show?package=cppcheck&project=Trunk cppcheck]
|arjan
|
|-
|[http://build.meego.com/package/show?package=cppunit&project=Trunk cppunit]
|
|
|-
|[http://build.meego.com/package/show?package=crda&project=Trunk crda]
|
|
|-
|[http://build.meego.com/package/show?package=createrepo&project=Trunk createrepo]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=cronie&project=Trunk cronie]
|yyang
|
|-
|[http://build.meego.com/package/show?package=crontabs&project=Trunk crontabs]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-binutils&project=Trunk cross-armv5tel-binutils]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-binutils-accel&project=Trunk cross-armv5tel-binutils-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-gcc&project=Trunk cross-armv5tel-gcc]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-gcc-accel&project=Trunk cross-armv5tel-gcc-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-binutils&project=Trunk cross-armv7hl-binutils]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-binutils-accel&project=Trunk cross-armv7hl-binutils-accel]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-gcc&project=Trunk cross-armv7hl-gcc]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-gcc-accel&project=Trunk cross-armv7hl-gcc-accel]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-binutils&project=Trunk cross-armv7l-binutils]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-binutils-accel&project=Trunk cross-armv7l-binutils-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-gcc&project=Trunk cross-armv7l-gcc]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-gcc-accel&project=Trunk cross-armv7l-gcc-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-platformfile&project=Trunk cross-armv7l-platformfile]
|cvm
|
|-
|[http://build.meego.com/package/show?package=cross-armv7tnhl-platformfile&project=Trunk cross-armv7tnhl-platformfile]
|cvm
|
|-
|[http://build.meego.com/package/show?package=cryptsetup-luks&project=Trunk cryptsetup-luks]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=cscope&project=Trunk cscope]
|
|
|-
|[http://build.meego.com/package/show?package=ctags&project=Trunk ctags]
|
|
|-
|[http://build.meego.com/package/show?package=ctdb&project=Trunk ctdb]
|
|
|-
|[http://build.meego.com/package/show?package=cups&project=Trunk cups]
|itachi
|
|-
|[http://build.meego.com/package/show?package=curl&project=Trunk curl]
|
|
|-
|[http://build.meego.com/package/show?package=cvs&project=Trunk cvs]
|
|
|-
|[http://build.meego.com/package/show?package=cyrus-sasl&project=Trunk cyrus-sasl]
|
|
|-
|[http://build.meego.com/package/show?package=d-feet&project=Trunk d-feet]
|
|
|-
|[http://build.meego.com/package/show?package=db4&project=Trunk db4]
|yyin2
|devel:base
|-
|[http://build.meego.com/package/show?package=db4-x86&project=Trunk db4-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=dblatex&project=Trunk dblatex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=dbus&project=Trunk dbus]
|huaxu
|devel:base
|-
|[http://build.meego.com/package/show?package=dbus-glib&project=Trunk dbus-glib]
|huaxu
|
|-
|[http://build.meego.com/package/show?package=dbus-python&project=Trunk dbus-python]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=dejagnu&project=Trunk dejagnu]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=dejavu-fonts&project=Trunk dejavu-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=deltarpm&project=Trunk deltarpm]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=desktop-backgrounds&project=Trunk desktop-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=desktop-file-utils&project=Trunk desktop-file-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=dev86&project=Trunk dev86]
|
|
|-
|[http://build.meego.com/package/show?package=devhelp&project=Trunk devhelp]
|jfding
|devel:gnome
|-
|[http://build.meego.com/package/show?package=device-mapper&project=Trunk device-mapper]
|yyang
|
|-
|[http://build.meego.com/package/show?package=device-mapper-multipath&project=Trunk device-mapper-multipath]
|yyang
|
|-
|[http://build.meego.com/package/show?package=dia&project=Trunk dia]
|
|
|-
|[http://build.meego.com/package/show?package=dialog&project=Trunk dialog]
|
|
|-
|[http://build.meego.com/package/show?package=diffstat&project=Trunk diffstat]
|yyang
|
|-
|[http://build.meego.com/package/show?package=diffutils&project=Trunk diffutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=diffutils-x86&project=Trunk diffutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=distcc&project=Trunk distcc]
|
|
|-
|[http://build.meego.com/package/show?package=djvulibre&project=Trunk djvulibre]
|
|
|-
|[http://build.meego.com/package/show?package=dmidecode&project=Trunk dmidecode]
|
|
|-
|[http://build.meego.com/package/show?package=dnsmasq&project=Trunk dnsmasq]
|martin
|
|-
|[http://build.meego.com/package/show?package=docbook-dtds&project=Trunk docbook-dtds]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-style-dsssl&project=Trunk docbook-style-dsssl]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-style-xsl&project=Trunk docbook-style-xsl]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-utils&project=Trunk docbook-utils]
|
|
|-
|[http://build.meego.com/package/show?package=dos2unix&project=Trunk dos2unix]
|
|
|-
|[http://build.meego.com/package/show?package=dosfstools&project=Trunk dosfstools]
|
|
|-
|[http://build.meego.com/package/show?package=dotconf&project=Trunk dotconf]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=doxygen&project=Trunk doxygen]
|
|
|-
|[http://build.meego.com/package/show?package=doxygen-x86&project=Trunk doxygen-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=doxymacs&project=Trunk doxymacs]
|
|
|-
|[http://build.meego.com/package/show?package=driconf&project=Trunk driconf]
|xyl
|
|-
|[http://build.meego.com/package/show?package=droid-fonts&project=Trunk droid-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=dropbear&project=Trunk dropbear]
|austin
|
|-
|[http://build.meego.com/package/show?package=dsme&project=Trunk dsme]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=dsp-tools&project=Trunk dsp-tools]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=dvd+rw-tools&project=Trunk dvd+rw-tools]
|
|
|-
|[http://build.meego.com/package/show?package=dvipdfm&project=Trunk dvipdfm]
|
|
|-
|[http://build.meego.com/package/show?package=dvipdfmx&project=Trunk dvipdfmx]
|yanli
|
|-
|[http://build.meego.com/package/show?package=dvipng&project=Trunk dvipng]
|
|
|-
|[http://build.meego.com/package/show?package=e2fsprogs&project=Trunk e2fsprogs]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=eat&project=Trunk eat]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=ecryptfs-utils&project=Trunk ecryptfs-utils]
|yanli
|
|-
|[http://build.meego.com/package/show?package=ed&project=Trunk ed]
|yyang
|
|-
|[http://build.meego.com/package/show?package=eggdbus&project=Trunk eggdbus]
|
|
|-
|[http://build.meego.com/package/show?package=eject&project=Trunk eject]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=elfutils&project=Trunk elfutils]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=elfutils-libelf-x86&project=Trunk elfutils-libelf-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=elfutils-libs-x86&project=Trunk elfutils-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=elfutils-x86&project=Trunk elfutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=emacs&project=Trunk emacs]
|
|
|-
|[http://build.meego.com/package/show?package=empathy&project=Trunk empathy]
|
|
|-
|[http://build.meego.com/package/show?package=enchant&project=Trunk enchant]
|
|
|-
|[http://build.meego.com/package/show?package=enscript&project=Trunk enscript]
|
|
|-
|[http://build.meego.com/package/show?package=eog&project=Trunk eog]
|
|
|-
|[http://build.meego.com/package/show?package=eog-plugins&project=Trunk eog-plugins]
|
|
|-
|[http://build.meego.com/package/show?package=eom&project=Trunk eom]
|
|
|-
|[http://build.meego.com/package/show?package=epydoc&project=Trunk epydoc]
|
|
|-
|[http://build.meego.com/package/show?package=esound&project=Trunk esound]
|
|
|-
|[http://build.meego.com/package/show?package=etherboot&project=Trunk etherboot]
|
|
|-
|[http://build.meego.com/package/show?package=ethtool&project=Trunk ethtool]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=evince&project=Trunk evince]
|
|
|-
|[http://build.meego.com/package/show?package=evolution&project=Trunk evolution]
|ross
|
|-
|[http://build.meego.com/package/show?package=evolution-data-server&project=Trunk evolution-data-server]
|
|
|-
|[http://build.meego.com/package/show?package=evtest&project=Trunk evtest]
|ulf
|
|-
|[http://build.meego.com/package/show?package=exempi&project=Trunk exempi]
|
|
|-
|[http://build.meego.com/package/show?package=exiv2&project=Trunk exiv2]
|
|
|-
|[http://build.meego.com/package/show?package=expat&project=Trunk expat]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=expect&project=Trunk expect]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=fakechroot&project=Trunk fakechroot]
|yyang
|
|-
|[http://build.meego.com/package/show?package=fakeroot&project=Trunk fakeroot]
|
|
|-
|[http://build.meego.com/package/show?package=farsight2&project=Trunk farsight2]
|
|
|-
|[http://build.meego.com/package/show?package=fastinit&project=Trunk fastinit]
|
|
|-
|[http://build.meego.com/package/show?package=fastjar&project=Trunk fastjar]
|austin
|
|-
|[http://build.meego.com/package/show?package=fdupes&project=Trunk fdupes]
|nashif
|
|-
|[http://build.meego.com/package/show?package=fdupes-x86&project=Trunk fdupes-x86]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=fennec-qt&project=Trunk fennec-qt]
|logoel
|
|-
|[http://build.meego.com/package/show?package=fennec-qt-branding-meego&project=Trunk fennec-qt-branding-meego]
|
|
|-
|[http://build.meego.com/package/show?package=fennec-taskswitcher-extension&project=Trunk fennec-taskswitcher-extension]
|logoel
|
|-
|[http://build.meego.com/package/show?package=festival&project=Trunk festival]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=festival-freebsoft-utils&project=Trunk festival-freebsoft-utils]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=file&project=Trunk file]
|
|
|-
|[http://build.meego.com/package/show?package=file-libs-x86&project=Trunk file-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=file-roller&project=Trunk file-roller]
|
|
|-
|[http://build.meego.com/package/show?package=file-x86&project=Trunk file-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=filesystem&project=Trunk filesystem]
|
|
|-
|[http://build.meego.com/package/show?package=findutils&project=Trunk findutils]
|yanli
|
|-
|[http://build.meego.com/package/show?package=findutils-x86&project=Trunk findutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=firstboot&project=Trunk firstboot]
|vivian
|
|-
|[http://build.meego.com/package/show?package=flac&project=Trunk flac]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=flex&project=Trunk flex]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=fontconfig&project=Trunk fontconfig]
|yanli
|
|-
|[http://build.meego.com/package/show?package=fontforge&project=Trunk fontforge]
|yanli
|
|-
|[http://build.meego.com/package/show?package=fontpackages&project=Trunk fontpackages]
|yanli
|
|-
|[http://build.meego.com/package/show?package=foomatic&project=Trunk foomatic]
|
|
|-
|[http://build.meego.com/package/show?package=foomatic-db&project=Trunk foomatic-db]
|
|
|-
|[http://build.meego.com/package/show?package=fortune-mod&project=Trunk fortune-mod]
|ulf
|
|-
|[http://build.meego.com/package/show?package=fprintd&project=Trunk fprintd]
|
|
|-
|[http://build.meego.com/package/show?package=freeglut&project=Trunk freeglut]
|xyl
|
|-
|[http://build.meego.com/package/show?package=freepats&project=Trunk freepats]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=freetype&project=Trunk freetype]
|
|
|-
|[http://build.meego.com/package/show?package=fribidi&project=Trunk fribidi]
|
|
|-
|[http://build.meego.com/package/show?package=frozen-bubble&project=Trunk frozen-bubble]
|
|
|-
|[http://build.meego.com/package/show?package=fslint&project=Trunk fslint]
|jiachenghu
|
|-
|[http://build.meego.com/package/show?package=fuse&project=Trunk fuse]
|
|
|-
|[http://build.meego.com/package/show?package=fuse-sshfs&project=Trunk fuse-sshfs]
|
|
|-
|[http://build.meego.com/package/show?package=fvkbd&project=Trunk fvkbd]
|
|
|-
|[http://build.meego.com/package/show?package=fw-update&project=Trunk fw-update]
|praj
|
|-
|[http://build.meego.com/package/show?package=gamin&project=Trunk gamin]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=gammu&project=Trunk gammu]
|boudra
|
|-
|[http://build.meego.com/package/show?package=garage-client-services&project=Trunk garage-client-services]
|jackiewu
|
|-
|[http://build.meego.com/package/show?package=garage-netbook-ui&project=Trunk garage-netbook-ui]
|jackiewu
|
|-
|[http://build.meego.com/package/show?package=gawk&project=Trunk gawk]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gawk-x86&project=Trunk gawk-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=gc&project=Trunk gc]
|
|
|-
|[http://build.meego.com/package/show?package=gcalctool&project=Trunk gcalctool]
|
|
|-
|[http://build.meego.com/package/show?package=gcc&project=Trunk gcc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gcc-cross&project=Trunk gcc-cross]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=gconf-editor&project=Trunk gconf-editor]
|
|
|-
|[http://build.meego.com/package/show?package=gd&project=Trunk gd]
|
|
|-
|[http://build.meego.com/package/show?package=gdb&project=Trunk gdb]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gdbm&project=Trunk gdbm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gdu-nautilus-extension&project=Trunk gdu-nautilus-extension]
|
|
|-
|[http://build.meego.com/package/show?package=gedit&project=Trunk gedit]
|
|
|-
|[http://build.meego.com/package/show?package=gegl&project=Trunk gegl]
|
|
|-
|[http://build.meego.com/package/show?package=generic-backgrounds&project=Trunk generic-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=generic-logos&project=Trunk generic-logos]
|
|
|-
|[http://build.meego.com/package/show?package=geoclue&project=Trunk geoclue]
|
|
|-
|[http://build.meego.com/package/show?package=gettext&project=Trunk gettext]
|
|
|-
|[http://build.meego.com/package/show?package=ghostscript&project=Trunk ghostscript]
|itachi
|
|-
|[http://build.meego.com/package/show?package=ghostscript-fonts&project=Trunk ghostscript-fonts]
|itachi
|
|-
|[http://build.meego.com/package/show?package=giflib&project=Trunk giflib]
|
|
|-
|[http://build.meego.com/package/show?package=gimp&project=Trunk gimp]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=git&project=Trunk git]
|
|
|-
|[http://build.meego.com/package/show?package=glade3&project=Trunk glade3]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gles-libs&project=Trunk gles-libs]
|boudra
|
|-
|[http://build.meego.com/package/show?package=glew&project=Trunk glew]
|
|
|-
|[http://build.meego.com/package/show?package=glib2&project=Trunk glib2]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=glibc&project=Trunk glibc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=glibc-arm&project=Trunk glibc-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-devel-arm&project=Trunk glibc-devel-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-headers-arm&project=Trunk glibc-headers-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-x86&project=Trunk glibc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=glibmm&project=Trunk glibmm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gmime&project=Trunk gmime]
|
|
|-
|[http://build.meego.com/package/show?package=gmp&project=Trunk gmp]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gmp-x86&project=Trunk gmp-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=gnet2&project=Trunk gnet2]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-bluetooth&project=Trunk gnome-bluetooth]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-common&project=Trunk gnome-common]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-control-center-netbook&project=Trunk gnome-control-center-netbook]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-desktop&project=Trunk gnome-desktop]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-disk-utility&project=Trunk gnome-disk-utility]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-doc-utils&project=Trunk gnome-doc-utils]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-games&project=Trunk gnome-games]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-icon-theme&project=Trunk gnome-icon-theme]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-keyring&project=Trunk gnome-keyring]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-media&project=Trunk gnome-media]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-menus&project=Trunk gnome-menus]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-mime-data&project=Trunk gnome-mime-data]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-packagekit&project=Trunk gnome-packagekit]
|quanxianwang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=gnome-panel&project=Trunk gnome-panel]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-python2&project=Trunk gnome-python2]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-python2-desktop&project=Trunk gnome-python2-desktop]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-screensaver&project=Trunk gnome-screensaver]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-session&project=Trunk gnome-session]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-settings-daemon&project=Trunk gnome-settings-daemon]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-sharp2&project=Trunk gnome-sharp2]
|mmeeks
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-terminal&project=Trunk gnome-terminal]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-themes&project=Trunk gnome-themes]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-user-docs&project=Trunk gnome-user-docs]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-user-share&project=Trunk gnome-user-share]
|ross
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-utils&project=Trunk gnome-utils]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-vfs2&project=Trunk gnome-vfs2]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnonlin&project=Trunk gnonlin]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gnu-efi&project=Trunk gnu-efi]
|
|
|-
|[http://build.meego.com/package/show?package=gnuchess&project=Trunk gnuchess]
|
|
|-
|[http://build.meego.com/package/show?package=gnumeric&project=Trunk gnumeric]
|
|
|-
|[http://build.meego.com/package/show?package=gnupg&project=Trunk gnupg]
|
|
|-
|[http://build.meego.com/package/show?package=gnupg2&project=Trunk gnupg2]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gnutls&project=Trunk gnutls]
|qzhao9,yanli
|devel:security
|-
|[http://build.meego.com/package/show?package=goffice&project=Trunk goffice]
|
|
|-
|[http://build.meego.com/package/show?package=google-gadgets&project=Trunk google-gadgets]
|wwang29
|
|-
|[http://build.meego.com/package/show?package=gperf&project=Trunk gperf]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gpgme&project=Trunk gpgme]
|
|
|-
|[http://build.meego.com/package/show?package=gphotofs&project=Trunk gphotofs]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=gpsbabel&project=Trunk gpsbabel]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gpsd&project=Trunk gpsd]
|
|
|-
|[http://build.meego.com/package/show?package=gpsdrive&project=Trunk gpsdrive]
|
|
|-
|[http://build.meego.com/package/show?package=graphviz&project=Trunk graphviz]
|
|
|-
|[http://build.meego.com/package/show?package=grep&project=Trunk grep]
|yanli
|
|-
|[http://build.meego.com/package/show?package=grilo&project=Trunk grilo]
|
|
|-
|[http://build.meego.com/package/show?package=grilo-plugins&project=Trunk grilo-plugins]
|
|
|-
|[http://build.meego.com/package/show?package=grisbi&project=Trunk grisbi]
|
|
|-
|[http://build.meego.com/package/show?package=groff&project=Trunk groff]
|
|
|-
|[http://build.meego.com/package/show?package=grub&project=Trunk grub]
|
|
|-
|[http://build.meego.com/package/show?package=grubby&project=Trunk grubby]
|yyang
|
|-
|[http://build.meego.com/package/show?package=gsl&project=Trunk gsl]
|rolla
|
|-
|[http://build.meego.com/package/show?package=gsm&project=Trunk gsm]
|
|
|-
|[http://build.meego.com/package/show?package=gssdp&project=Trunk gssdp]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gst-dsp&project=Trunk gst-dsp]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-bad-free&project=Trunk gst-plugins-bad-free]
|bgao1,lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-base&project=Trunk gst-plugins-base]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-camera&project=Trunk gst-plugins-camera]
|vivian
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-dvbsub&project=Trunk gst-plugins-dvbsub]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-farsight&project=Trunk gst-plugins-farsight]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-flumpegdemux&project=Trunk gst-plugins-flumpegdemux]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-good&project=Trunk gst-plugins-good]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-teletext&project=Trunk gst-plugins-teletext]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-va&project=Trunk gst-plugins-va]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gst-v4l2-camsrc&project=Trunk gst-v4l2-camsrc]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-vabuffer&project=Trunk gst-vabuffer]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gstreamer&project=Trunk gstreamer]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gstreamer-editing-services&project=Trunk gstreamer-editing-services]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gstreamer-python&project=Trunk gstreamer-python]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gthumb&project=Trunk gthumb]
|
|
|-
|[http://build.meego.com/package/show?package=gtk-doc&project=Trunk gtk-doc]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtk-nodoka-engine&project=Trunk gtk-nodoka-engine]
|
|
|-
|[http://build.meego.com/package/show?package=gtk-sharp2&project=Trunk gtk-sharp2]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=gtk2&project=Trunk gtk2]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gtk2-engines&project=Trunk gtk2-engines]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtkglext&project=Trunk gtkglext]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtkhtml3&project=Trunk gtkhtml3]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gtkmathview&project=Trunk gtkmathview]
|
|
|-
|[http://build.meego.com/package/show?package=gtkmm&project=Trunk gtkmm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtksourceview2&project=Trunk gtksourceview2]
|
|
|-
|[http://build.meego.com/package/show?package=gtkspell&project=Trunk gtkspell]
|
|
|-
|[http://build.meego.com/package/show?package=guile&project=Trunk guile]
|
|
|-
|[http://build.meego.com/package/show?package=gupnp&project=Trunk gupnp]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-av&project=Trunk gupnp-av]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-dlna&project=Trunk gupnp-dlna]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gupnp-igd&project=Trunk gupnp-igd]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-tools&project=Trunk gupnp-tools]
|
|
|-
|[http://build.meego.com/package/show?package=gupnp-ui&project=Trunk gupnp-ui]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-vala&project=Trunk gupnp-vala]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gvfs&project=Trunk gvfs]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=gwenhywfar&project=Trunk gwenhywfar]
|
|
|-
|[http://build.meego.com/package/show?package=gypsy&project=Trunk gypsy]
|
|
|-
|[http://build.meego.com/package/show?package=gzip&project=Trunk gzip]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gzip-x86&project=Trunk gzip-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=hardlink&project=Trunk hardlink]
|yyang
|
|-
|[http://build.meego.com/package/show?package=help2man&project=Trunk help2man]
|
|
|-
|[http://build.meego.com/package/show?package=hfdialer&project=Trunk hfdialer]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=hfdialer-branding-meego&project=Trunk hfdialer-branding-meego]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=hfp&project=Trunk hfp]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=hicolor-icon-theme&project=Trunk hicolor-icon-theme]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=html2ps&project=Trunk html2ps]
|
|
|-
|[http://build.meego.com/package/show?package=hunspell&project=Trunk hunspell]
|
|
|-
|[http://build.meego.com/package/show?package=hunspell-en&project=Trunk hunspell-en]
|
|
|-
|[http://build.meego.com/package/show?package=hwdata&project=Trunk hwdata]
|
|
|-
|[http://build.meego.com/package/show?package=i2c-tools&project=Trunk i2c-tools]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=iasl&project=Trunk iasl]
|
|
|-
|[http://build.meego.com/package/show?package=icon-naming-utils&project=Trunk icon-naming-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=icu&project=Trunk icu]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=ilmbase&project=Trunk ilmbase]
|
|
|-
|[http://build.meego.com/package/show?package=image-configurations&project=Trunk image-configurations]
|nashif
|
|-
|[http://build.meego.com/package/show?package=image-manager&project=Trunk image-manager]
|yyang
|
|-
|[http://build.meego.com/package/show?package=imake&project=Trunk imake]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=indent&project=Trunk indent]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=inkscape&project=Trunk inkscape]
|
|
|-
|[http://build.meego.com/package/show?package=inotify-tools&project=Trunk inotify-tools]
|
|
|-
|[http://build.meego.com/package/show?package=installer&project=Trunk installer]
|vivian
|
|-
|[http://build.meego.com/package/show?package=installer-shell&project=Trunk installer-shell]
|vivian
|
|-
|[http://build.meego.com/package/show?package=intel-gpu-tools&project=Trunk intel-gpu-tools]
|pli1,xyl
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=intltool&project=Trunk intltool]
|
|
|-
|[http://build.meego.com/package/show?package=iproute&project=Trunk iproute]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iptables&project=Trunk iptables]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iputils&project=Trunk iputils]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iso-codes&project=Trunk iso-codes]
|
|
|-
|[http://build.meego.com/package/show?package=isomd5sum&project=Trunk isomd5sum]
|yyang
|
|-
|[http://build.meego.com/package/show?package=ividesktop&project=Trunk ividesktop]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=ivihome&project=Trunk ivihome]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=iw&project=Trunk iw]
|
|
|-
|[http://build.meego.com/package/show?package=jadetex&project=Trunk jadetex]
|
|
|-
|[http://build.meego.com/package/show?package=jana&project=Trunk jana]
|
|
|-
|[http://build.meego.com/package/show?package=jasper&project=Trunk jasper]
|
|
|-
|[http://build.meego.com/package/show?package=joe&project=Trunk joe]
|
|
|-
|[http://build.meego.com/package/show?package=joystick&project=Trunk joystick]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=json-c&project=Trunk json-c]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=json-glib&project=Trunk json-glib]
|
|
|-
|[http://build.meego.com/package/show?package=kasumi&project=Trunk kasumi]
|
|
|-
|[http://build.meego.com/package/show?package=kbd&project=Trunk kbd]
|
|
|-
|[http://build.meego.com/package/show?package=kcalcore&project=Trunk kcalcore]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=kde-mobile&project=Trunk kde-mobile]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=kernel&project=Trunk kernel]
|
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-connext&project=Trunk kernel-adaptation-connext]
|
|
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-intel-automotive&project=Trunk kernel-adaptation-intel-automotive]
|qi
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-medfield&project=Trunk kernel-adaptation-medfield]
|ldmai
|
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-mrst&project=Trunk kernel-adaptation-mrst]
|arjan
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-n900&project=Trunk kernel-adaptation-n900]
|ikoskine
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-oaktrail&project=Trunk kernel-adaptation-oaktrail]
|kai
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-headers&project=Trunk kernel-headers]
|arjan
|
|-
|[http://build.meego.com/package/show?package=kernel-headers-arm&project=Trunk kernel-headers-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=kexec-tools&project=Trunk kexec-tools]
|apalande
|
|-
|[http://build.meego.com/package/show?package=keycodes-setup&project=Trunk keycodes-setup]
|ulf
|
|-
|[http://build.meego.com/package/show?package=keyutils&project=Trunk keyutils]
|
|
|-
|[http://build.meego.com/package/show?package=kickstarter&project=Trunk kickstarter]
|nashif
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=kmod-virtiogl&project=Trunk kmod-virtiogl]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=krb5&project=Trunk krb5]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=ladspa&project=Trunk ladspa]
|
|
|-
|[http://build.meego.com/package/show?package=lapack&project=Trunk lapack]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=latencytop&project=Trunk latencytop]
|arjan
|
|-
|[http://build.meego.com/package/show?package=latex2html&project=Trunk latex2html]
|
|
|-
|[http://build.meego.com/package/show?package=lcms&project=Trunk lcms]
|
|
|-
|[http://build.meego.com/package/show?package=less&project=Trunk less]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=lftp&project=Trunk lftp]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=libCI&project=Trunk libCI]
|ulf
|
|-
|[http://build.meego.com/package/show?package=libICE&project=Trunk libICE]
|
|
|-
|[http://build.meego.com/package/show?package=libIDL&project=Trunk libIDL]
|
|
|-
|[http://build.meego.com/package/show?package=libSM&project=Trunk libSM]
|
|
|-
|[http://build.meego.com/package/show?package=libX11&project=Trunk libX11]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXScrnSaver&project=Trunk libXScrnSaver]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXTrap&project=Trunk libXTrap]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXau&project=Trunk libXau]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXaw&project=Trunk libXaw]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXcomposite&project=Trunk libXcomposite]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXcursor&project=Trunk libXcursor]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXdamage&project=Trunk libXdamage]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXdmcp&project=Trunk libXdmcp]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXevie&project=Trunk libXevie]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXext&project=Trunk libXext]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXfixes&project=Trunk libXfixes]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXfont&project=Trunk libXfont]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXfontcache&project=Trunk libXfontcache]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXft&project=Trunk libXft]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXi&project=Trunk libXi]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXinerama&project=Trunk libXinerama]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXmu&project=Trunk libXmu]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXpm&project=Trunk libXpm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXrandr&project=Trunk libXrandr]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXrender&project=Trunk libXrender]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXres&project=Trunk libXres]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXt&project=Trunk libXt]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXtst&project=Trunk libXtst]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXv&project=Trunk libXv]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXvMC&project=Trunk libXvMC]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXxf86dga&project=Trunk libXxf86dga]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXxf86misc&project=Trunk libXxf86misc]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXxf86vm&project=Trunk libXxf86vm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libaccounts-glib&project=Trunk libaccounts-glib]
|bwachter,pcapriotti
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libaccounts-qt&project=Trunk libaccounts-qt]
|bwachter,pcapriotti
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libaccounts-ui&project=Trunk libaccounts-ui]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libacl-x86&project=Trunk libacl-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libao&project=Trunk libao]
|
|
|-
|[http://build.meego.com/package/show?package=libarchive&project=Trunk libarchive]
|
|
|-
|[http://build.meego.com/package/show?package=libart_lgpl&project=Trunk libart_lgpl]
|
|
|-
|[http://build.meego.com/package/show?package=libassuan&project=Trunk libassuan]
|
|
|-
|[http://build.meego.com/package/show?package=libasyncns&project=Trunk libasyncns]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libatasmart&project=Trunk libatasmart]
|
|
|-
|[http://build.meego.com/package/show?package=libatomic_ops&project=Trunk libatomic_ops]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=libattr-x86&project=Trunk libattr-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libbonobo&project=Trunk libbonobo]
|
|
|-
|[http://build.meego.com/package/show?package=libbonoboui&project=Trunk libbonoboui]
|
|
|-
|[http://build.meego.com/package/show?package=libburn&project=Trunk libburn]
|
|
|-
|[http://build.meego.com/package/show?package=libcanberra&project=Trunk libcanberra]
|vivian
|
|-
|[http://build.meego.com/package/show?package=libcap&project=Trunk libcap]
|
|
|-
|[http://build.meego.com/package/show?package=libcap-ng&project=Trunk libcap-ng]
|
|
|-
|[http://build.meego.com/package/show?package=libcap-x86&project=Trunk libcap-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libchamplain&project=Trunk libchamplain]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=libchewing&project=Trunk libchewing]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libcmtspeech-ifx&project=Trunk libcmtspeech-ifx]
|vivian
|
|-
|[http://build.meego.com/package/show?package=libcmtspeechdata&project=Trunk libcmtspeechdata]
|
|
|-
|[http://build.meego.com/package/show?package=libcommhistory&project=Trunk libcommhistory]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libcontentaction&project=Trunk libcontentaction]
|maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=libcqpid&project=Trunk libcqpid]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=libcreds3&project=Trunk libcreds3]
|peter,rrware
|
|-
|[http://build.meego.com/package/show?package=libcroco&project=Trunk libcroco]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libdaemon&project=Trunk libdaemon]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libdbus-c++&project=Trunk libdbus-c++]
|huaxu
|
|-
|[http://build.meego.com/package/show?package=libdiscid&project=Trunk libdiscid]
|
|
|-
|[http://build.meego.com/package/show?package=libdmx&project=Trunk libdmx]
|
|
|-
|[http://build.meego.com/package/show?package=libdres&project=Trunk libdres]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libdrm&project=Trunk libdrm]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=libdsme&project=Trunk libdsme]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libedit&project=Trunk libedit]
|
|
|-
|[http://build.meego.com/package/show?package=libeigen2&project=Trunk libeigen2]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=libenca&project=Trunk libenca]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=liberation-fonts&project=Trunk liberation-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=libevent&project=Trunk libevent]
|
|
|-
|[http://build.meego.com/package/show?package=libexif&project=Trunk libexif]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libfakekey&project=Trunk libfakekey]
|
|
|-
|[http://build.meego.com/package/show?package=libffi&project=Trunk libffi]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libfontenc&project=Trunk libfontenc]
|yanli
|
|-
|[http://build.meego.com/package/show?package=libfprint&project=Trunk libfprint]
|
|
|-
|[http://build.meego.com/package/show?package=libgail-gnome&project=Trunk libgail-gnome]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgcc-x86&project=Trunk libgcc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=libgcrypt&project=Trunk libgcrypt]
|
|
|-
|[http://build.meego.com/package/show?package=libgda&project=Trunk libgda]
|
|
|-
|[http://build.meego.com/package/show?package=libgdata&project=Trunk libgdata]
|daihan
|
|-
|[http://build.meego.com/package/show?package=libgdbus&project=Trunk libgdbus]
|
|
|-
|[http://build.meego.com/package/show?package=libgdiplus0&project=Trunk libgdiplus0]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=libgdl&project=Trunk libgdl]
|
|
|-
|[http://build.meego.com/package/show?package=libgee&project=Trunk libgee]
|
|
|-
|[http://build.meego.com/package/show?package=libggz&project=Trunk libggz]
|
|
|-
|[http://build.meego.com/package/show?package=libglade2&project=Trunk libglade2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libglademm&project=Trunk libglademm]
|
|
|-
|[http://build.meego.com/package/show?package=libgnome&project=Trunk libgnome]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnome-keyring&project=Trunk libgnome-keyring]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomecanvas&project=Trunk libgnomecanvas]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomecups&project=Trunk libgnomecups]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomekbd&project=Trunk libgnomekbd]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomeprint22&project=Trunk libgnomeprint22]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomeprintui22&project=Trunk libgnomeprintui22]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomeui&project=Trunk libgnomeui]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgpg-error&project=Trunk libgpg-error]
|
|
|-
|[http://build.meego.com/package/show?package=libgphoto2&project=Trunk libgphoto2]
|
|
|-
|[http://build.meego.com/package/show?package=libgsf&project=Trunk libgsf]
|
|
|-
|[http://build.meego.com/package/show?package=libgtop2&project=Trunk libgtop2]
|
|
|-
|[http://build.meego.com/package/show?package=libgweather&project=Trunk libgweather]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libhangul&project=Trunk libhangul]
|
|
|-
|[http://build.meego.com/package/show?package=libical&project=Trunk libical]
|boudra
|
|-
|[http://build.meego.com/package/show?package=libid3tag&project=Trunk libid3tag]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libidn&project=Trunk libidn]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libiodata&project=Trunk libiodata]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libiphb&project=Trunk libiphb]
|
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libiptcdata&project=Trunk libiptcdata]
|zivchang
|
|-
|[http://build.meego.com/package/show?package=libisofs&project=Trunk libisofs]
|
|
|-
|[http://build.meego.com/package/show?package=libjingle&project=Trunk libjingle]
|
|
|-
|[http://build.meego.com/package/show?package=libjpeg&project=Trunk libjpeg]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libksba&project=Trunk libksba]
|yanli
|
|-
|[http://build.meego.com/package/show?package=liblua-x86&project=Trunk liblua-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libmatchbox&project=Trunk libmatchbox]
|
|
|-
|[http://build.meego.com/package/show?package=libmeegochat&project=Trunk libmeegochat]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libmeegotouch&project=Trunk libmeegotouch]
|msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libmikmod&project=Trunk libmikmod]
|
|
|-
|[http://build.meego.com/package/show?package=libmlocknice&project=Trunk libmlocknice]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=libmng&project=Trunk libmng]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libmp4v2&project=Trunk libmp4v2]
|
|
|-
|[http://build.meego.com/package/show?package=libmtp&project=Trunk libmtp]
|
|
|-
|[http://build.meego.com/package/show?package=libngf&project=Trunk libngf]
|mantyharju
|
|-
|[http://build.meego.com/package/show?package=libnice&project=Trunk libnice]
|
|
|-
|[http://build.meego.com/package/show?package=libnl&project=Trunk libnl]
|
|
|-
|[http://build.meego.com/package/show?package=libnotify&project=Trunk libnotify]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libofono-qt&project=Trunk libofono-qt]
|sbryan,boudra
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=libofx&project=Trunk libofx]
|
|
|-
|[http://build.meego.com/package/show?package=libogg&project=Trunk libogg]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=liboil&project=Trunk liboil]
|
|
|-
|[http://build.meego.com/package/show?package=libopenraw&project=Trunk libopenraw]
|
|
|-
|[http://build.meego.com/package/show?package=libopensync&project=Trunk libopensync]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libopensync-plugin-vformat&project=Trunk libopensync-plugin-vformat]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libpaper&project=Trunk libpaper]
|
|
|-
|[http://build.meego.com/package/show?package=libpcap&project=Trunk libpcap]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=libpciaccess&project=Trunk libpciaccess]
|
|
|-
|[http://build.meego.com/package/show?package=libpng&project=Trunk libpng]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libprolog&project=Trunk libprolog]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libpthread-stubs&project=Trunk libpthread-stubs]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libqmlog&project=Trunk libqmlog]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libqterminalmode&project=Trunk libqterminalmode]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libqtsparql&project=Trunk libqtsparql]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=libqtsparql-tracker-extensions&project=Trunk libqtsparql-tracker-extensions]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=libqttracker&project=Trunk libqttracker]
|rusty,lamadon,maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=libquill&project=Trunk libquill]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=libquillmetadata&project=Trunk libquillmetadata]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=librapi2&project=Trunk librapi2]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=librds&project=Trunk librds]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libresource&project=Trunk libresource]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libresourceqt&project=Trunk libresourceqt]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=librsvg2&project=Trunk librsvg2]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsamplerate&project=Trunk libsamplerate]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsatsolver&project=Trunk libsatsolver]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=libseaside&project=Trunk libseaside]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=libsexy&project=Trunk libsexy]
|
|
|-
|[http://build.meego.com/package/show?package=libshare-ui&project=Trunk libshare-ui]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=libsigc++&project=Trunk libsigc++]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libsignon&project=Trunk libsignon]
|bwachter,pcapriotti
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libsignon-glib&project=Trunk libsignon-glib]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libsignoncrypto-qt&project=Trunk libsignoncrypto-qt]
|mardy,pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libsilc&project=Trunk libsilc]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libsmack&project=Trunk libsmack]
|rrware
|devel:security
|-
|[http://build.meego.com/package/show?package=libsmbios&project=Trunk libsmbios]
|
|
|-
|[http://build.meego.com/package/show?package=libsndfile&project=Trunk libsndfile]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsocialweb&project=Trunk libsocialweb]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=libsocialweb-keys&project=Trunk libsocialweb-keys]
|
|
|-
|[http://build.meego.com/package/show?package=libsocialweb-qml&project=Trunk libsocialweb-qml]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libsocialweb-qt&project=Trunk libsocialweb-qt]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libsoup&project=Trunk libsoup]
|
|
|-
|[http://build.meego.com/package/show?package=libspectre&project=Trunk libspectre]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libspiro&project=Trunk libspiro]
|
|
|-
|[http://build.meego.com/package/show?package=libstdc++-x86&project=Trunk libstdc++-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libsynce&project=Trunk libsynce]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libsyncml&project=Trunk libsyncml]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libtalloc&project=Trunk libtalloc]
|
|
|-
|[http://build.meego.com/package/show?package=libtar&project=Trunk libtar]
|
|
|-
|[http://build.meego.com/package/show?package=libtasn1&project=Trunk libtasn1]
|
|
|-
|[http://build.meego.com/package/show?package=libtdb&project=Trunk libtdb]
|
|
|-
|[http://build.meego.com/package/show?package=libtdb-compat&project=Trunk libtdb-compat]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libtee&project=Trunk libtee]
|rrware
|
|-
|[http://build.meego.com/package/show?package=libtelepathy&project=Trunk libtelepathy]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=libthai&project=Trunk libthai]
|
|
|-
|[http://build.meego.com/package/show?package=libtheora&project=Trunk libtheora]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libthumbnailer&project=Trunk libthumbnailer]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=libtiff&project=Trunk libtiff]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libtool&project=Trunk libtool]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libtrace&project=Trunk libtrace]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libuninameslist&project=Trunk libuninameslist]
|
|
|-
|[http://build.meego.com/package/show?package=libusb&project=Trunk libusb]
|
|
|-
|[http://build.meego.com/package/show?package=libusb1&project=Trunk libusb1]
|
|
|-
|[http://build.meego.com/package/show?package=libuser&project=Trunk libuser]
|
|
|-
|[http://build.meego.com/package/show?package=libutempter&project=Trunk libutempter]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libv4l&project=Trunk libv4l]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libva&project=Trunk libva]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libvisual&project=Trunk libvisual]
|
|
|-
|[http://build.meego.com/package/show?package=libvorbis&project=Trunk libvorbis]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libwbxml2&project=Trunk libwbxml2]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=libwmf&project=Trunk libwmf]
|
|
|-
|[http://build.meego.com/package/show?package=libwnck&project=Trunk libwnck]
|
|
|-
|[http://build.meego.com/package/show?package=libwpd&project=Trunk libwpd]
|
|
|-
|[http://build.meego.com/package/show?package=libwpg&project=Trunk libwpg]
|
|
|-
|[http://build.meego.com/package/show?package=libwps&project=Trunk libwps]
|
|
|-
|[http://build.meego.com/package/show?package=libwsbm&project=Trunk libwsbm]
|
|
|-
|[http://build.meego.com/package/show?package=libxcb&project=Trunk libxcb]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libxkbfile&project=Trunk libxkbfile]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libxklavier&project=Trunk libxklavier]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libxml2&project=Trunk libxml2]
|nashif
|
|-
|[http://build.meego.com/package/show?package=libxml2-python&project=Trunk libxml2-python]
|nashif
|
|-
|[http://build.meego.com/package/show?package=libxslt&project=Trunk libxslt]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libzip&project=Trunk libzip]
|yyang
|
|-
|[http://build.meego.com/package/show?package=libzypp&project=Trunk libzypp]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=libzypp-bindings&project=Trunk libzypp-bindings]
|yyang
|
|-
|[http://build.meego.com/package/show?package=link-grammar&project=Trunk link-grammar]
|
|
|-
|[http://build.meego.com/package/show?package=linux-firmware&project=Trunk linux-firmware]
|
|
|-
|[http://build.meego.com/package/show?package=lirc&project=Trunk lirc]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=lklug-fonts&project=Trunk lklug-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lockdev&project=Trunk lockdev]
|
|
|-
|[http://build.meego.com/package/show?package=logrotate&project=Trunk logrotate]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-assamese-fonts&project=Trunk lohit-assamese-fonts]
|vivian
|
|-
|[http://build.meego.com/package/show?package=lohit-bengali-fonts&project=Trunk lohit-bengali-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-gujarati-fonts&project=Trunk lohit-gujarati-fonts]
|haoli
|
|-
|[http://build.meego.com/package/show?package=lohit-hindi-fonts&project=Trunk lohit-hindi-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-kannada-fonts&project=Trunk lohit-kannada-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-malayalam-fonts&project=Trunk lohit-malayalam-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-oriya-fonts&project=Trunk lohit-oriya-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-punjabi-fonts&project=Trunk lohit-punjabi-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-tamil-fonts&project=Trunk lohit-tamil-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-telugu-fonts&project=Trunk lohit-telugu-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=loudmouth&project=Trunk loudmouth]
|
|
|-
|[http://build.meego.com/package/show?package=lpsolve&project=Trunk lpsolve]
|
|
|-
|[http://build.meego.com/package/show?package=lrzsz&project=Trunk lrzsz]
|
|
|-
|[http://build.meego.com/package/show?package=lsof&project=Trunk lsof]
|
|
|-
|[http://build.meego.com/package/show?package=ltrace&project=Trunk ltrace]
|
|
|-
|[http://build.meego.com/package/show?package=lua&project=Trunk lua]
|jfding
|
|-
|[http://build.meego.com/package/show?package=lzo&project=Trunk lzo]
|yyang
|
|-
|[http://build.meego.com/package/show?package=m17n-contrib&project=Trunk m17n-contrib]
|
|
|-
|[http://build.meego.com/package/show?package=m17n-db&project=Trunk m17n-db]
|
|
|-
|[http://build.meego.com/package/show?package=m17n-lib&project=Trunk m17n-lib]
|
|
|-
|[http://build.meego.com/package/show?package=m2crypto&project=Trunk m2crypto]
|
|devel:security
|-
|[http://build.meego.com/package/show?package=m4&project=Trunk m4]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mad-developer&project=Trunk mad-developer]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=maemo-video-thumbnailer&project=Trunk maemo-video-thumbnailer]
|dlespiau,lamadon,maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=mailcap&project=Trunk mailcap]
|
|
|-
|[http://build.meego.com/package/show?package=mailx&project=Trunk mailx]
|
|
|-
|[http://build.meego.com/package/show?package=make&project=Trunk make]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=makebootfat&project=Trunk makebootfat]
|
|
|-
|[http://build.meego.com/package/show?package=man&project=Trunk man]
|
|
|-
|[http://build.meego.com/package/show?package=man-pages&project=Trunk man-pages]
|
|
|-
|[http://build.meego.com/package/show?package=marble&project=Trunk marble]
|
|
|-
|[http://build.meego.com/package/show?package=marmazon&project=Trunk marmazon]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=matchbox-keyboard&project=Trunk matchbox-keyboard]
|
|
|-
|[http://build.meego.com/package/show?package=matchbox-panel&project=Trunk matchbox-panel]
|
|
|-
|[http://build.meego.com/package/show?package=matchbox-window-manager&project=Trunk matchbox-window-manager]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=mathml-fonts&project=Trunk mathml-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=mce&project=Trunk mce]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=mce-headers&project=Trunk mce-headers]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=meego-accelerator&project=Trunk meego-accelerator]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-bookmarks&project=Trunk meego-bookmarks]
|
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv5tel-sysroot&project=Trunk meego-cross-armv5tel-sysroot]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv7hl-sysroot&project=Trunk meego-cross-armv7hl-sysroot]
|austin
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv7l-sysroot&project=Trunk meego-cross-armv7l-sysroot]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-cursor-theme&project=Trunk meego-cursor-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meego-handset-calendar&project=Trunk meego-handset-calendar]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-chat&project=Trunk meego-handset-chat]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-configs&project=Trunk meego-handset-configs]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer&project=Trunk meego-handset-dialer]
|sbryan,ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer-branding-meego&project=Trunk meego-handset-dialer-branding-meego]
|sbryan,ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer-translations&project=Trunk meego-handset-dialer-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-email&project=Trunk meego-handset-email]
|ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-email-translations&project=Trunk meego-handset-email-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-icon-theme&project=Trunk meego-handset-icon-theme]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-mannequin&project=Trunk meego-handset-mannequin]
|sbryan,ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-music&project=Trunk meego-handset-music]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-music-branding-meego&project=Trunk meego-handset-music-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-people&project=Trunk meego-handset-people]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-photos&project=Trunk meego-handset-photos]
|krupert,ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-photos-branding-meego&project=Trunk meego-handset-photos-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-sms&project=Trunk meego-handset-sms]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-sms-translations&project=Trunk meego-handset-sms-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-socialweb&project=Trunk meego-handset-socialweb]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-sound-theme&project=Trunk meego-handset-sound-theme]
|ulf,tracyg
|
|-
|[http://build.meego.com/package/show?package=meego-handset-video&project=Trunk meego-handset-video]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-video-branding-meego&project=Trunk meego-handset-video-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-ivi-configs&project=Trunk meego-ivi-configs]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=meego-lsb&project=Trunk meego-lsb]
|nashif
|
|-
|[http://build.meego.com/package/show?package=meego-menus&project=Trunk meego-menus]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-help&project=Trunk meego-netbook-help]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-intro&project=Trunk meego-netbook-intro]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-settings&project=Trunk meego-netbook-settings]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-theme&project=Trunk meego-netbook-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-user-skel&project=Trunk meego-netbook-user-skel]
|
|
|-
|[http://build.meego.com/package/show?package=meego-osc-plugins&project=Trunk meego-osc-plugins]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=meego-packaging-tools&project=Trunk meego-packaging-tools]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=meego-panel-applications&project=Trunk meego-panel-applications]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-datetime&project=Trunk meego-panel-datetime]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-devices&project=Trunk meego-panel-devices]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-myzone&project=Trunk meego-panel-myzone]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-networks&project=Trunk meego-panel-networks]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-pasteboard&project=Trunk meego-panel-pasteboard]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-people&project=Trunk meego-panel-people]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-status&project=Trunk meego-panel-status]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-web&project=Trunk meego-panel-web]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-zones&project=Trunk meego-panel-zones]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-release&project=Trunk meego-release]
|nashif
|
|-
|[http://build.meego.com/package/show?package=meego-rpm-config&project=Trunk meego-rpm-config]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=meego-sdk-qemugl-addon&project=Trunk meego-sdk-qemugl-addon]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=meego-simulator-launcher&project=Trunk meego-simulator-launcher]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=meego-sound-theme&project=Trunk meego-sound-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meegotouch-applauncherd&project=Trunk meegotouch-applauncherd]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-applifed&project=Trunk meegotouch-applifed]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-compositor&project=Trunk meegotouch-compositor]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-controlpanel&project=Trunk meegotouch-controlpanel]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-controlpanelapplets&project=Trunk meegotouch-controlpanelapplets]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-feedback&project=Trunk meegotouch-feedback]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-feedbackreactionmaps&project=Trunk meegotouch-feedbackreactionmaps]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-home&project=Trunk meegotouch-home]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodbridges&project=Trunk meegotouch-inputmethodbridges]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodengine&project=Trunk meegotouch-inputmethodengine]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodframework&project=Trunk meegotouch-inputmethodframework]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodkeyboard&project=Trunk meegotouch-inputmethodkeyboard]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-qt-style&project=Trunk meegotouch-qt-style]
|boudra
|
|-
|[http://build.meego.com/package/show?package=meegotouch-systemtui&project=Trunk meegotouch-systemtui]
|
|
|-
|[http://build.meego.com/package/show?package=meegotouch-systemui&project=Trunk meegotouch-systemui]
|krupert,araujo
|
|-
|[http://build.meego.com/package/show?package=meegotouch-theme&project=Trunk meegotouch-theme]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-theme-meego&project=Trunk meegotouch-theme-meego]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-bluetooth&project=Trunk meegotouchcp-bluetooth]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-chat&project=Trunk meegotouchcp-chat]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-connman&project=Trunk meegotouchcp-connman]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-datetime&project=Trunk meegotouchcp-datetime]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-language&project=Trunk meegotouchcp-language]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-regionformat&project=Trunk meegotouchcp-regionformat]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-socialweb&project=Trunk meegotouchcp-socialweb]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-ux-translations&project=Trunk meego-ux-translations]
|pmccarty
|devel:meego-ux
|-
|[http://build.meego.com/package/show?package=meld&project=Trunk meld]
|
|
|-
|[http://build.meego.com/package/show?package=memuse&project=Trunk memuse]
|arjan
|
|-
|[http://build.meego.com/package/show?package=mesa&project=Trunk mesa]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=mesa-demos&project=Trunk mesa-demos]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=mic2&project=Trunk mic2]
|yyang
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=min&project=Trunk min]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=mingetty&project=Trunk mingetty]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=minicom&project=Trunk minicom]
|
|
|-
|[http://build.meego.com/package/show?package=mkcal&project=Trunk mkcal]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=mkdevnodes&project=Trunk mkdevnodes]
|
|
|-
|[http://build.meego.com/package/show?package=mkinitrd&project=Trunk mkinitrd]
|yyang
|
|-
|[http://build.meego.com/package/show?package=mlocate&project=Trunk mlocate]
|
|
|-
|[http://build.meego.com/package/show?package=mm-common&project=Trunk mm-common]
|
|
|-
|[http://build.meego.com/package/show?package=mobile-broadband-provider-info&project=Trunk mobile-broadband-provider-info]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-generic-backgrounds&project=Trunk moblin-generic-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-icon-theme&project=Trunk moblin-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-live&project=Trunk moblin-live]
|
|
|-
|[http://build.meego.com/package/show?package=module-init-tools&project=Trunk module-init-tools]
|
|
|-
|[http://build.meego.com/package/show?package=monit&project=Trunk monit]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=monitor-call-audio-setting-mid&project=Trunk monitor-call-audio-setting-mid]
|vivian
|
|-
|[http://build.meego.com/package/show?package=mono-addins&project=Trunk mono-addins]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=mono-core&project=Trunk mono-core]
|priya
|
|-
|[http://build.meego.com/package/show?package=mono-zeroconf&project=Trunk mono-zeroconf]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=mozilla-filesystem&project=Trunk mozilla-filesystem]
|jfding
|
|-
|[http://build.meego.com/package/show?package=mpage&project=Trunk mpage]
|
|
|-
|[http://build.meego.com/package/show?package=mpc&project=Trunk mpc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mpc-x86&project=Trunk mpc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=mpfr&project=Trunk mpfr]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mpfr-x86&project=Trunk mpfr-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=mssf-certman&project=Trunk mssf-certman]
|rrware
|
|-
|[http://build.meego.com/package/show?package=mssf-crypto&project=Trunk mssf-crypto]
|rrware
|
|-
|[http://build.meego.com/package/show?package=mtd-utils&project=Trunk mtd-utils]
|
|
|-
|[http://build.meego.com/package/show?package=mtdev&project=Trunk mtdev]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=mtools&project=Trunk mtools]
|yyang
|
|-
|[http://build.meego.com/package/show?package=mutter&project=Trunk mutter]
|tomas
|devel:clutter
|-
|[http://build.meego.com/package/show?package=mutter-netbook&project=Trunk mutter-netbook]
|
|
|-
|[http://build.meego.com/package/show?package=mx&project=Trunk mx]
|
|
|-
|[http://build.meego.com/package/show?package=n900-camera-firmware&project=Trunk n900-camera-firmware]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nano&project=Trunk nano]
|
|
|-
|[http://build.meego.com/package/show?package=nasm&project=Trunk nasm]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=nautilus&project=Trunk nautilus]
|
|
|-
|[http://build.meego.com/package/show?package=nautilus-python&project=Trunk nautilus-python]
|
|
|-
|[http://build.meego.com/package/show?package=navit&project=Trunk navit]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=navit-maps&project=Trunk navit-maps]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=nc&project=Trunk nc]
|
|
|-
|[http://build.meego.com/package/show?package=ncurses&project=Trunk ncurses]
|jfding
|
|-
|[http://build.meego.com/package/show?package=ncurses-libs-x86&project=Trunk ncurses-libs-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=ndesk-dbus&project=Trunk ndesk-dbus]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=ndesk-dbus-glib&project=Trunk ndesk-dbus-glib]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=neon&project=Trunk neon]
|jfding
|
|-
|[http://build.meego.com/package/show?package=net-tools&project=Trunk net-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=netbook-backgrounds&project=Trunk netbook-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=netbook-icon-theme&project=Trunk netbook-icon-theme]
|hbons
|
|-
|[http://build.meego.com/package/show?package=netpbm&project=Trunk netpbm]
|
|
|-
|[http://build.meego.com/package/show?package=neverball&project=Trunk neverball]
|
|
|-
|[http://build.meego.com/package/show?package=newt&project=Trunk newt]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=newt-python&project=Trunk newt-python]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=ngfd&project=Trunk ngfd]
|mantyharju
|
|-
|[http://build.meego.com/package/show?package=nodoka-theme-gnome&project=Trunk nodoka-theme-gnome]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=nokia-n900-configs&project=Trunk nokia-n900-configs]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nokia-n900-rescue-initrd&project=Trunk nokia-n900-rescue-initrd]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nokia-usb-networking&project=Trunk nokia-usb-networking]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=notification-daemon&project=Trunk notification-daemon]
|
|
|-
|[http://build.meego.com/package/show?package=notification-daemon-engine-nodoka&project=Trunk notification-daemon-engine-nodoka]
|
|
|-
|[http://build.meego.com/package/show?package=notify-python&project=Trunk notify-python]
|
|
|-
|[http://build.meego.com/package/show?package=notify-sharp&project=Trunk notify-sharp]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=nspr&project=Trunk nspr]
|jfding
|devel:base
|-
|[http://build.meego.com/package/show?package=nspr-x86&project=Trunk nspr-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=nss&project=Trunk nss]
|qzhao9
|devel:base
|-
|[http://build.meego.com/package/show?package=nss-mdns&project=Trunk nss-mdns]
|
|
|-
|[http://build.meego.com/package/show?package=nss-softokn-freebl-x86&project=Trunk nss-softokn-freebl-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=nss-x86&project=Trunk nss-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=ntp&project=Trunk ntp]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=o3read&project=Trunk o3read]
|
|
|-
|[http://build.meego.com/package/show?package=obex-data-server&project=Trunk obex-data-server]
|
|
|-
|[http://build.meego.com/package/show?package=obexd&project=Trunk obexd]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=ofono&project=Trunk ofono]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=ohm&project=Trunk ohm]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=ohm-plugins-misc&project=Trunk ohm-plugins-misc]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=opal&project=Trunk opal]
|
|
|-
|[http://build.meego.com/package/show?package=openconnect&project=Trunk openconnect]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=opengl-games-utils&project=Trunk opengl-games-utils]
|
|
|-
|[http://build.meego.com/package/show?package=openjade&project=Trunk openjade]
|
|
|-
|[http://build.meego.com/package/show?package=openjpeg&project=Trunk openjpeg]
|
|
|-
|[http://build.meego.com/package/show?package=openldap&project=Trunk openldap]
|
|
|-
|[http://build.meego.com/package/show?package=openobex&project=Trunk openobex]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=opensp&project=Trunk opensp]
|
|
|-
|[http://build.meego.com/package/show?package=openssh&project=Trunk openssh]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=openssl&project=Trunk openssl]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=openssl-certs&project=Trunk openssl-certs]
|
|
|-
|[http://build.meego.com/package/show?package=openvpn&project=Trunk openvpn]
|martin
|
|-
|[http://build.meego.com/package/show?package=orc&project=Trunk orc]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=org-mode&project=Trunk org-mode]
|
|
|-
|[http://build.meego.com/package/show?package=osc&project=Trunk osc]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=ots&project=Trunk ots]
|
|
|-
|[http://build.meego.com/package/show?package=package-groups&project=Trunk package-groups]
|nashif
|
|-
|[http://build.meego.com/package/show?package=pacrunner&project=Trunk pacrunner]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=pakchois&project=Trunk pakchois]
|
|
|-
|[http://build.meego.com/package/show?package=pam&project=Trunk pam]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=pam_pkcs11&project=Trunk pam_pkcs11]
|
|
|-
|[http://build.meego.com/package/show?package=pango&project=Trunk pango]
|
|
|-
|[http://build.meego.com/package/show?package=pangomm&project=Trunk pangomm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=paps&project=Trunk paps]
|
|
|-
|[http://build.meego.com/package/show?package=papyon&project=Trunk papyon]
|lixu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=parted&project=Trunk parted]
|vivian
|
|-
|[http://build.meego.com/package/show?package=passivetex&project=Trunk passivetex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=passwd&project=Trunk passwd]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=patch&project=Trunk patch]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=patch-x86&project=Trunk patch-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=patchelf&project=Trunk patchelf]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=patchutils&project=Trunk patchutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=pavucontrol&project=Trunk pavucontrol]
|vivian
|
|-
|[http://build.meego.com/package/show?package=pax&project=Trunk pax]
|
|
|-
|[http://build.meego.com/package/show?package=pciutils&project=Trunk pciutils]
|
|
|-
|[http://build.meego.com/package/show?package=pcre&project=Trunk pcre]
|
|
|-
|[http://build.meego.com/package/show?package=perl&project=Trunk perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Archive-Zip&project=Trunk perl-Archive-Zip]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Array-Compare&project=Trunk perl-Array-Compare]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Config-IniFiles&project=Trunk perl-Config-IniFiles]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Convert-ASN1&project=Trunk perl-Convert-ASN1]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Convert-BinHex&project=Trunk perl-Convert-BinHex]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Crypt-SSLeay&project=Trunk perl-Crypt-SSLeay]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Date-Manip&project=Trunk perl-Date-Manip]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Devel-StackTrace&project=Trunk perl-Devel-StackTrace]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Devel-Symdump&project=Trunk perl-Devel-Symdump]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Error&project=Trunk perl-Error]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-Depends&project=Trunk perl-ExtUtils-Depends]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-MakeMaker-Coverage&project=Trunk perl-ExtUtils-MakeMaker-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-PkgConfig&project=Trunk perl-ExtUtils-PkgConfig]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-BaseDir&project=Trunk perl-File-BaseDir]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-DesktopEntry&project=Trunk perl-File-DesktopEntry]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-MimeInfo&project=Trunk perl-File-MimeInfo]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-Which&project=Trunk perl-File-Which]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Finance-Quote&project=Trunk perl-Finance-Quote]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Font-TTF&project=Trunk perl-Font-TTF]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Glib&project=Trunk perl-Glib]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Parser&project=Trunk perl-HTML-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-TableExtract&project=Trunk perl-HTML-TableExtract]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Tagset&project=Trunk perl-HTML-Tagset]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Tree&project=Trunk perl-HTML-Tree]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-Socket-INET6&project=Trunk perl-IO-Socket-INET6]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-Socket-SSL&project=Trunk perl-IO-Socket-SSL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-stringy&project=Trunk perl-IO-stringy]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-JSON&project=Trunk perl-JSON]
|qzhao9,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=perl-MIME-Lite&project=Trunk perl-MIME-Lite]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-MIME-tools&project=Trunk perl-MIME-tools]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-MailTools&project=Trunk perl-MailTools]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-LibIDN&project=Trunk perl-Net-LibIDN]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-SMTP-SSL&project=Trunk perl-Net-SMTP-SSL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-SSLeay&project=Trunk perl-Net-SSLeay]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Parse-Yapp&project=Trunk perl-Parse-Yapp]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Pod-Coverage&project=Trunk perl-Pod-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SDL&project=Trunk perl-SDL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SGMLSpm&project=Trunk perl-SGMLSpm]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SOAP-Lite&project=Trunk perl-SOAP-Lite]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SVG&project=Trunk perl-SVG]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SVG-Parser&project=Trunk perl-SVG-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Socket6&project=Trunk perl-Socket6]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Sub-Uplevel&project=Trunk perl-Sub-Uplevel]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Exception&project=Trunk perl-Test-Exception]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-MockObject&project=Trunk perl-Test-MockObject]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-NoWarnings&project=Trunk perl-Test-NoWarnings]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Number-Delta&project=Trunk perl-Test-Number-Delta]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Pod&project=Trunk perl-Test-Pod]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Pod-Coverage&project=Trunk perl-Test-Pod-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Tester&project=Trunk perl-Test-Tester]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Warn&project=Trunk perl-Test-Warn]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Text-Unidecode&project=Trunk perl-Text-Unidecode]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tie-IxHash&project=Trunk perl-Tie-IxHash]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-TimeDate&project=Trunk perl-TimeDate]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tk&project=Trunk perl-Tk]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tree-DAG_Node&project=Trunk perl-Tree-DAG_Node]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-UNIVERSAL-can&project=Trunk perl-UNIVERSAL-can]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-UNIVERSAL-isa&project=Trunk perl-UNIVERSAL-isa]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-URI&project=Trunk perl-URI]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-DOM&project=Trunk perl-XML-DOM]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-LibXML&project=Trunk perl-XML-LibXML]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-NamespaceSupport&project=Trunk perl-XML-NamespaceSupport]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-Parser&project=Trunk perl-XML-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-RegExp&project=Trunk perl-XML-RegExp]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-SAX&project=Trunk perl-XML-SAX]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-Simple&project=Trunk perl-XML-Simple]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-TreeBuilder&project=Trunk perl-XML-TreeBuilder]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-XQL&project=Trunk perl-XML-XQL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-YAML&project=Trunk perl-YAML]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-gettext&project=Trunk perl-gettext]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-libwww-perl&project=Trunk perl-libwww-perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-libxml-perl&project=Trunk perl-libxml-perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=persistman&project=Trunk persistman]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=phidgetlinux&project=Trunk phidgetlinux]
|xing
|
|-
|[http://build.meego.com/package/show?package=phonesim&project=Trunk phonesim]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=phonon&project=Trunk phonon]
|xiaoqiang,quanxianwang,boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=pidgin&project=Trunk pidgin]
|
|
|-
|[http://build.meego.com/package/show?package=pidgin-sipe&project=Trunk pidgin-sipe]
|
|
|-
|[http://build.meego.com/package/show?package=pixman&project=Trunk pixman]
|xyl
|
|-
|[http://build.meego.com/package/show?package=pkcs11-helper&project=Trunk pkcs11-helper]
|martin
|
|-
|[http://build.meego.com/package/show?package=pkgconfig&project=Trunk pkgconfig]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=plib&project=Trunk plib]
|
|
|-
|[http://build.meego.com/package/show?package=plymouth-lite&project=Trunk plymouth-lite]
|
|
|-
|[http://build.meego.com/package/show?package=pm-utils&project=Trunk pm-utils]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=pmtools&project=Trunk pmtools]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=pocketsphinx&project=Trunk pocketsphinx]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=poedit&project=Trunk poedit]
|
|
|-
|[http://build.meego.com/package/show?package=policy-settings-basic-mfld&project=Trunk policy-settings-basic-mfld]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=policy-settings-basic-n900&project=Trunk policy-settings-basic-n900]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=policy-settings-tablet&project=Trunk policy-settings-tablet]
|
|
|-
|[http://build.meego.com/package/show?package=polkit&project=Trunk polkit]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=polkit-gnome&project=Trunk polkit-gnome]
|yyin2
|devel:gnome
|-
|[http://build.meego.com/package/show?package=poppler&project=Trunk poppler]
|xiaoqiang,quanxianwang,boudra
|
|-
|[http://build.meego.com/package/show?package=poppler-data&project=Trunk poppler-data]
|boudra
|
|-
|[http://build.meego.com/package/show?package=poppler-qt&project=Trunk poppler-qt]
|boudra
|
|-
|[http://build.meego.com/package/show?package=popt&project=Trunk popt]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=popt-x86&project=Trunk popt-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=post-build-checks&project=Trunk post-build-checks]
|nashif
|
|-
|[http://build.meego.com/package/show?package=poster&project=Trunk poster]
|
|
|-
|[http://build.meego.com/package/show?package=powerstatemgr&project=Trunk powerstatemgr]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=powertop&project=Trunk powertop]
|arjan
|
|-
|[http://build.meego.com/package/show?package=ppl&project=Trunk ppl]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=ppp&project=Trunk ppp]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=prelink&project=Trunk prelink]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=procps&project=Trunk procps]
|
|
|-
|[http://build.meego.com/package/show?package=psb-headers&project=Trunk psb-headers]
|
|
|-
|[http://build.meego.com/package/show?package=psmisc&project=Trunk psmisc]
|yyang
|
|-
|[http://build.meego.com/package/show?package=psutils&project=Trunk psutils]
|
|
|-
|[http://build.meego.com/package/show?package=pth&project=Trunk pth]
|
|
|-
|[http://build.meego.com/package/show?package=ptlib&project=Trunk ptlib]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pulseaudio&project=Trunk pulseaudio]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-meego&project=Trunk pulseaudio-modules-meego]
|
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-mfld&project=Trunk pulseaudio-modules-mfld]
|ulf
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-n900&project=Trunk pulseaudio-modules-n900]
|
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-policy-enforcement&project=Trunk pulseaudio-policy-enforcement]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-settings-mfld&project=Trunk pulseaudio-settings-mfld]
|
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-settings-n900&project=Trunk pulseaudio-settings-n900]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=pyOpenSSL&project=Trunk pyOpenSSL]
|
|
|-
|[http://build.meego.com/package/show?package=pycairo&project=Trunk pycairo]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pyclutter&project=Trunk pyclutter]
|rbradford,ebassi
|devel:clutter
|-
|[http://build.meego.com/package/show?package=pyclutter-gtk&project=Trunk pyclutter-gtk]
|rbradford,ebassi
|devel:clutter
|-
|[http://build.meego.com/package/show?package=pygobject2&project=Trunk pygobject2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygpgme&project=Trunk pygpgme]
|
|
|-
|[http://build.meego.com/package/show?package=pygtk2&project=Trunk pygtk2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygtkglext&project=Trunk pygtkglext]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygtksourceview&project=Trunk pygtksourceview]
|
|
|-
|[http://build.meego.com/package/show?package=pykickstart&project=Trunk pykickstart]
|vivian
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=pyorbit&project=Trunk pyorbit]
|
|
|-
|[http://build.meego.com/package/show?package=pyparted&project=Trunk pyparted]
|vivian
|
|-
|[http://build.meego.com/package/show?package=python&project=Trunk python]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-Coherence&project=Trunk python-Coherence]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-ZSI&project=Trunk python-ZSI]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-adns&project=Trunk python-adns]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-chardet&project=Trunk python-chardet]
|jiachenghu
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-cheetah&project=Trunk python-cheetah]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-configobj&project=Trunk python-configobj]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-crypto&project=Trunk python-crypto]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-dateutil&project=Trunk python-dateutil]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-decorator&project=Trunk python-decorator]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-docutils&project=Trunk python-docutils]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-dtopt&project=Trunk python-dtopt]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-enchant&project=Trunk python-enchant]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-formencode&project=Trunk python-formencode]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-fpconst&project=Trunk python-fpconst]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-gdata&project=Trunk python-gdata]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-imaging&project=Trunk python-imaging]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-iniparse&project=Trunk python-iniparse]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-louie&project=Trunk python-louie]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-lxml&project=Trunk python-lxml]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-magic&project=Trunk python-magic]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-markdown&project=Trunk python-markdown]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-mutagen&project=Trunk python-mutagen]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-nose&project=Trunk python-nose]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-numeric&project=Trunk python-numeric]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-paste&project=Trunk python-paste]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-paste-deploy&project=Trunk python-paste-deploy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-pycurl&project=Trunk python-pycurl]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-pygments&project=Trunk python-pygments]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-reportlab&project=Trunk python-reportlab]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-setuptools&project=Trunk python-setuptools]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-sexy&project=Trunk python-sexy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-simplejson&project=Trunk python-simplejson]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-sqlite2&project=Trunk python-sqlite2]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-telepathy&project=Trunk python-telepathy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-tempita&project=Trunk python-tempita]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-toscawidgets&project=Trunk python-toscawidgets]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-tw-forms&project=Trunk python-tw-forms]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted&project=Trunk python-twisted]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-conch&project=Trunk python-twisted-conch]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-core&project=Trunk python-twisted-core]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-lore&project=Trunk python-twisted-lore]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-mail&project=Trunk python-twisted-mail]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-names&project=Trunk python-twisted-names]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-news&project=Trunk python-twisted-news]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-runner&project=Trunk python-twisted-runner]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-web&project=Trunk python-twisted-web]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-web2&project=Trunk python-twisted-web2]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-words&project=Trunk python-twisted-words]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-urlgrabber&project=Trunk python-urlgrabber]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-webob&project=Trunk python-webob]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-which&project=Trunk python-which]
|
|
|-
|[http://build.meego.com/package/show?package=python-wsgiproxy&project=Trunk python-wsgiproxy]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-xklavier&project=Trunk python-xklavier]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-zope-filesystem&project=Trunk python-zope-filesystem]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-zope-interface&project=Trunk python-zope-interface]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=pytz&project=Trunk pytz]
|
|
|-
|[http://build.meego.com/package/show?package=pyxdg&project=Trunk pyxdg]
|jiachenghu
|
|-
|[http://build.meego.com/package/show?package=qca2&project=Trunk qca2]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qca2-ossl&project=Trunk qca2-ossl]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qjson&project=Trunk qjson]
|rusty
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qmf&project=Trunk qmf]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qmsystem&project=Trunk qmsystem]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=qpid-cpp&project=Trunk qpid-cpp]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=qt&project=Trunk qt]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-creator&project=Trunk qt-creator]
|priya,boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-mobility&project=Trunk qt-mobility]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-mobility-geoservices-cloudmade&project=Trunk qt-mobility-geoservices-cloudmade]
|mikeleib
|
|-
|[http://build.meego.com/package/show?package=qt-mobility-mediaservice-dbus&project=Trunk qt-mobility-mediaservice-dbus]
|
|
|-
|[http://build.meego.com/package/show?package=qt-obex-ftp-library&project=Trunk qt-obex-ftp-library]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qtcontacts-tracker&project=Trunk qtcontacts-tracker]
|
|devel:people
|-
|[http://build.meego.com/package/show?package=qterminalmodeclient&project=Trunk qterminalmodeclient]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=qtgstreamer&project=Trunk qtgstreamer]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=qttas-server&project=Trunk qttas-server]
|talahtel
|
|-
|[http://build.meego.com/package/show?package=qtwebkit&project=Trunk qtwebkit]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=quicksynergy&project=Trunk quicksynergy]
|
|
|-
|[http://build.meego.com/package/show?package=quillimagefilter&project=Trunk quillimagefilter]
|
|
|-
|[http://build.meego.com/package/show?package=quilt&project=Trunk quilt]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rar-kernel-headers&project=Trunk rar-kernel-headers]
|ulf
|
|-
|[http://build.meego.com/package/show?package=rarian&project=Trunk rarian]
|
|
|-
|[http://build.meego.com/package/show?package=rdsd&project=Trunk rdsd]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=rdsquery&project=Trunk rdsquery]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=readline&project=Trunk readline]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=recode&project=Trunk recode]
|
|
|-
|[http://build.meego.com/package/show?package=rest&project=Trunk rest]
|ross
|
|-
|[http://build.meego.com/package/show?package=rfkill&project=Trunk rfkill]
|erwanmahe
|
|-
|[http://build.meego.com/package/show?package=rhpl&project=Trunk rhpl]
|vivian
|
|-
|[http://build.meego.com/package/show?package=rhythmbox&project=Trunk rhythmbox]
|
|
|-
|[http://build.meego.com/package/show?package=rootfiles&project=Trunk rootfiles]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpm&project=Trunk rpm]
|nashif,xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=rpm-build-x86&project=Trunk rpm-build-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpm-libs-x86&project=Trunk rpm-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpm-python&project=Trunk rpm-python]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpm-x86&project=Trunk rpm-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpmcheck&project=Trunk rpmcheck]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmdevtools&project=Trunk rpmdevtools]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmlint&project=Trunk rpmlint]
|nashif
|devel:building
|-
|[http://build.meego.com/package/show?package=rpmlint-Moblin&project=Trunk rpmlint-Moblin]
|nashif
|devel:building
|-
|[http://build.meego.com/package/show?package=rpmlint-mini&project=Trunk rpmlint-mini]
|nashif
|devel:building
|-
|[http://build.meego.com/package/show?package=rpmlint-mini-x86&project=Trunk rpmlint-mini-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpmorphan&project=Trunk rpmorphan]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmreaper&project=Trunk rpmreaper]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rsync&project=Trunk rsync]
|
|
|-
|[http://build.meego.com/package/show?package=rtkit&project=Trunk rtkit]
|yyang
|
|-
|[http://build.meego.com/package/show?package=ruby&project=Trunk ruby]
|jfding
|
|-
|[http://build.meego.com/package/show?package=rygel&project=Trunk rygel]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=samba&project=Trunk samba]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=sample-media&project=Trunk sample-media]
|auke
|
|-
|[http://build.meego.com/package/show?package=sane-backends&project=Trunk sane-backends]
|
|
|-
|[http://build.meego.com/package/show?package=scim&project=Trunk scim]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-anthy&project=Trunk scim-anthy]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-bridge&project=Trunk scim-bridge]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-chewing&project=Trunk scim-chewing]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-hangul&project=Trunk scim-hangul]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-m17n&project=Trunk scim-m17n]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-panel-vkb-gtk&project=Trunk scim-panel-vkb-gtk]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-pinyin&project=Trunk scim-pinyin]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-skk&project=Trunk scim-skk]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scons&project=Trunk scons]
|
|
|-
|[http://build.meego.com/package/show?package=screen&project=Trunk screen]
|nashif
|
|-
|[http://build.meego.com/package/show?package=sed&project=Trunk sed]
|yanli
|
|-
|[http://build.meego.com/package/show?package=sed-x86&project=Trunk sed-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=sensorfw&project=Trunk sensorfw]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=sensorfw-pegatron&project=Trunk sensorfw-pegatron]
|
|
|-
|[http://build.meego.com/package/show?package=setup&project=Trunk setup]
|
|
|-
|[http://build.meego.com/package/show?package=setuptool&project=Trunk setuptool]
|
|
|-
|[http://build.meego.com/package/show?package=sg3_utils&project=Trunk sg3_utils]
|
|
|-
|[http://build.meego.com/package/show?package=sgml-common&project=Trunk sgml-common]
|
|
|-
|[http://build.meego.com/package/show?package=shadow-utils&project=Trunk shadow-utils]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=shared-mime-info&project=Trunk shared-mime-info]
|vivian
|
|-
|[http://build.meego.com/package/show?package=sharutils&project=Trunk sharutils]
|yyang
|
|-
|[http://build.meego.com/package/show?package=signon-digest&project=Trunk signon-digest]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=signon-oauth2&project=Trunk signon-oauth2]
|senko,pcapriotti
|
|-
|[http://build.meego.com/package/show?package=simple-scan&project=Trunk simple-scan]
|
|
|-
|[http://build.meego.com/package/show?package=skkdic&project=Trunk skkdic]
|
|
|-
|[http://build.meego.com/package/show?package=slang&project=Trunk slang]
|
|
|-
|[http://build.meego.com/package/show?package=slib&project=Trunk slib]
|
|
|-
|[http://build.meego.com/package/show?package=smartmontools&project=Trunk smartmontools]
|
|
|-
|[http://build.meego.com/package/show?package=smem&project=Trunk smem]
|auke
|
|-
|[http://build.meego.com/package/show?package=smshistory&project=Trunk smshistory]
|krupert,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=sofia-sip&project=Trunk sofia-sip]
|
|
|-
|[http://build.meego.com/package/show?package=sound-theme-freedesktop&project=Trunk sound-theme-freedesktop]
|
|
|-
|[http://build.meego.com/package/show?package=soundtouch&project=Trunk soundtouch]
|
|
|-
|[http://build.meego.com/package/show?package=spectacle&project=Trunk spectacle]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=speech-dispatcher&project=Trunk speech-dispatcher]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=speex&project=Trunk speex]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=sphinxbase&project=Trunk sphinxbase]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=sqlite&project=Trunk sqlite]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sqlite-x86&project=Trunk sqlite-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=squashfs-tools&project=Trunk squashfs-tools]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sreadahead&project=Trunk sreadahead]
|auke
|
|-
|[http://build.meego.com/package/show?package=ssmtp&project=Trunk ssmtp]
|
|
|-
|[http://build.meego.com/package/show?package=startup-notification&project=Trunk startup-notification]
|jfding
|
|-
|[http://build.meego.com/package/show?package=strace&project=Trunk strace]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=subversion&project=Trunk subversion]
|
|
|-
|[http://build.meego.com/package/show?package=sudo&project=Trunk sudo]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=swi-prolog&project=Trunk swi-prolog]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=swig&project=Trunk swig]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=syncevolution&project=Trunk syncevolution]
|pohly
|
|-
|[http://build.meego.com/package/show?package=syncevolution-gtk&project=Trunk syncevolution-gtk]
|pohly
|
|-
|[http://build.meego.com/package/show?package=synergy&project=Trunk synergy]
|
|
|-
|[http://build.meego.com/package/show?package=sysfsutils&project=Trunk sysfsutils]
|
|
|-
|[http://build.meego.com/package/show?package=sysklogd&project=Trunk sysklogd]
|
|
|-
|[http://build.meego.com/package/show?package=syslinux&project=Trunk syslinux]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sysprof&project=Trunk sysprof]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-boot&project=Trunk system-config-boot]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=system-config-date&project=Trunk system-config-date]
|vivian
|
|-
|[http://build.meego.com/package/show?package=system-config-date-docs&project=Trunk system-config-date-docs]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=system-config-language&project=Trunk system-config-language]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-printer&project=Trunk system-config-printer]
|itachi
|
|-
|[http://build.meego.com/package/show?package=system-config-users&project=Trunk system-config-users]
|
|
|-
|[http://build.meego.com/package/show?package=sysvinit&project=Trunk sysvinit]
|
|
|-
|[http://build.meego.com/package/show?package=t1lib&project=Trunk t1lib]
|
|
|-
|[http://build.meego.com/package/show?package=taglib&project=Trunk taglib]
|
|
|-
|[http://build.meego.com/package/show?package=taglib-sharp&project=Trunk taglib-sharp]
|abock
|
|-
|[http://build.meego.com/package/show?package=tar&project=Trunk tar]
|yanli
|
|-
|[http://build.meego.com/package/show?package=tar-x86&project=Trunk tar-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=tasks&project=Trunk tasks]
|
|
|-
|[http://build.meego.com/package/show?package=tcl&project=Trunk tcl]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tcp_wrappers&project=Trunk tcp_wrappers]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tcpdump&project=Trunk tcpdump]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tcsh&project=Trunk tcsh]
|
|
|-
|[http://build.meego.com/package/show?package=teckit&project=Trunk teckit]
|
|
|-
|[http://build.meego.com/package/show?package=telepathy-butterfly&project=Trunk telepathy-butterfly]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-farsight&project=Trunk telepathy-farsight]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-filesystem&project=Trunk telepathy-filesystem]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-gabble&project=Trunk telepathy-gabble]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-glib&project=Trunk telepathy-glib]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-haze&project=Trunk telepathy-haze]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-idle&project=Trunk telepathy-idle]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-logger&project=Trunk telepathy-logger]
|zabaluev,rbradford
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-mission-control&project=Trunk telepathy-mission-control]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-qt4&project=Trunk telepathy-qt4]
|zabaluev
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-ring&project=Trunk telepathy-ring]
|bwachter
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-salut&project=Trunk telepathy-salut]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-sofiasip&project=Trunk telepathy-sofiasip]
|bwachter,zabaluev,pcapriotti
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-stream-engine&project=Trunk telepathy-stream-engine]
|senko
|
|-
|[http://build.meego.com/package/show?package=test-definition&project=Trunk test-definition]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=testrunner-lite&project=Trunk testrunner-lite]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=texi2html&project=Trunk texi2html]
|
|
|-
|[http://build.meego.com/package/show?package=texinfo&project=Trunk texinfo]
|
|
|-
|[http://build.meego.com/package/show?package=texlive&project=Trunk texlive]
|yanli
|
|-
|[http://build.meego.com/package/show?package=texlive-texmf&project=Trunk texlive-texmf]
|yanli
|
|-
|[http://build.meego.com/package/show?package=texlive-texmf-errata&project=Trunk texlive-texmf-errata]
|yanli
|
|-
|[http://build.meego.com/package/show?package=ti-kfmapp&project=Trunk ti-kfmapp]
|danisr
|
|-
|[http://build.meego.com/package/show?package=ti-uim&project=Trunk ti-uim]
|erwanmahe
|
|-
|[http://build.meego.com/package/show?package=tig&project=Trunk tig]
|
|
|-
|[http://build.meego.com/package/show?package=time&project=Trunk time]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=timed&project=Trunk timed]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=tinycdb&project=Trunk tinycdb]
|rusty
|
|-
|[http://build.meego.com/package/show?package=tix&project=Trunk tix]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tk&project=Trunk tk]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tmpwatch&project=Trunk tmpwatch]
|
|
|-
|[http://build.meego.com/package/show?package=tone-generator&project=Trunk tone-generator]
|
|
|-
|[http://build.meego.com/package/show?package=totem&project=Trunk totem]
|
|
|-
|[http://build.meego.com/package/show?package=totem-pl-parser&project=Trunk totem-pl-parser]
|
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=tpm-tools&project=Trunk tpm-tools]
|
|
|-
|[http://build.meego.com/package/show?package=traceroute&project=Trunk traceroute]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tracker&project=Trunk tracker]
|lamadon
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=tracker-upnp&project=Trunk tracker-upnp]
|jku
|devel:tv
|-
|[http://build.meego.com/package/show?package=transfer-ui&project=Trunk transfer-ui]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=transifex-client&project=Trunk transifex-client]
|auke
|
|-
|[http://build.meego.com/package/show?package=transmission&project=Trunk transmission]
|
|
|-
|[http://build.meego.com/package/show?package=trousers&project=Trunk trousers]
|
|
|-
|[http://build.meego.com/package/show?package=tsc2007-config&project=Trunk tsc2007-config]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=ttmkfdir&project=Trunk ttmkfdir]
|
|
|-
|[http://build.meego.com/package/show?package=tumbler&project=Trunk tumbler]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=twitter-glib&project=Trunk twitter-glib]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=tzdata&project=Trunk tzdata]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=u-boot&project=Trunk u-boot]
|nm
|
|-
|[http://build.meego.com/package/show?package=udev&project=Trunk udev]
|kai,zhongxin
|devel:udev
|-
|[http://build.meego.com/package/show?package=udev-rules-handset-mid&project=Trunk udev-rules-handset-mid]
|
|
|-
|[http://build.meego.com/package/show?package=udev-rules-netbook&project=Trunk udev-rules-netbook]
|
|
|-
|[http://build.meego.com/package/show?package=udev-rules-nokia-n900&project=Trunk udev-rules-nokia-n900]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=udiskie&project=Trunk udiskie]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=udisks&project=Trunk udisks]
|vivian,yyin2,zhongxin
|
|-
|[http://build.meego.com/package/show?package=udisks-helper-extras&project=Trunk udisks-helper-extras]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=un-core-fonts&project=Trunk un-core-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=unique&project=Trunk unique]
|
|
|-
|[http://build.meego.com/package/show?package=unzip&project=Trunk unzip]
|yyang
|
|-
|[http://build.meego.com/package/show?package=upower&project=Trunk upower]
|yyin2,zhongxin
|
|-
|[http://build.meego.com/package/show?package=urw-fonts&project=Trunk urw-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=usb-modeswitch&project=Trunk usb-modeswitch]
|
|
|-
|[http://build.meego.com/package/show?package=usb-modeswitch-data&project=Trunk usb-modeswitch-data]
|
|
|-
|[http://build.meego.com/package/show?package=usbutils&project=Trunk usbutils]
|
|
|-
|[http://build.meego.com/package/show?package=usermode&project=Trunk usermode]
|
|
|-
|[http://build.meego.com/package/show?package=usleep&project=Trunk usleep]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=utfs&project=Trunk utfs]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=uthash&project=Trunk uthash]
|rrware
|
|-
|[http://build.meego.com/package/show?package=util-linux-ng&project=Trunk util-linux-ng]
|yanli
|
|-
|[http://build.meego.com/package/show?package=uuid&project=Trunk uuid]
|
|
|-
|[http://build.meego.com/package/show?package=uxlaunch&project=Trunk uxlaunch]
|auke
|
|-
|[http://build.meego.com/package/show?package=v8&project=Trunk v8]
|
|devel:browser
|-
|[http://build.meego.com/package/show?package=vala&project=Trunk vala]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=valgrind&project=Trunk valgrind]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=vamp-plugin-sdk&project=Trunk vamp-plugin-sdk]
|
|
|-
|[http://build.meego.com/package/show?package=vibrant-icon-theme&project=Trunk vibrant-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=vim&project=Trunk vim]
|
|
|-
|[http://build.meego.com/package/show?package=vlgothic-fonts&project=Trunk vlgothic-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=voicecallhistory&project=Trunk voicecallhistory]
|krupert,ulf
|
|-
|[http://build.meego.com/package/show?package=vorbis-tools&project=Trunk vorbis-tools]
|
|
|-
|[http://build.meego.com/package/show?package=vpnc&project=Trunk vpnc]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=vte&project=Trunk vte]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=w3m&project=Trunk w3m]
|
|
|-
|[http://build.meego.com/package/show?package=webupload-engine&project=Trunk webupload-engine]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=wget&project=Trunk wget]
|jfding
|
|-
|[http://build.meego.com/package/show?package=wildmidi&project=Trunk wildmidi]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=wimax-tools&project=Trunk wimax-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wireless-regdb&project=Trunk wireless-regdb]
|cleech
|
|-
|[http://build.meego.com/package/show?package=wireless-tools&project=Trunk wireless-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wlanconfig&project=Trunk wlanconfig]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wpa_supplicant&project=Trunk wpa_supplicant]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wv&project=Trunk wv]
|
|
|-
|[http://build.meego.com/package/show?package=wxGTK&project=Trunk wxGTK]
|
|
|-
|[http://build.meego.com/package/show?package=wxPython&project=Trunk wxPython]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xbacklight&project=Trunk xbacklight]
|
|
|-
|[http://build.meego.com/package/show?package=xbindkeys&project=Trunk xbindkeys]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xcb-proto&project=Trunk xcb-proto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xcb-util&project=Trunk xcb-util]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xdg-user-dirs&project=Trunk xdg-user-dirs]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xdg-user-dirs-gtk&project=Trunk xdg-user-dirs-gtk]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xdg-utils&project=Trunk xdg-utils]
|xiaoqiang,quanxianwang,boudra
|
|-
|[http://build.meego.com/package/show?package=xdvipdfmx&project=Trunk xdvipdfmx]
|
|
|-
|[http://build.meego.com/package/show?package=xerces-c&project=Trunk xerces-c]
|
|
|-
|[http://build.meego.com/package/show?package=xhtml1-dtds&project=Trunk xhtml1-dtds]
|
|
|-
|[http://build.meego.com/package/show?package=xhtml2fo-style-xsl&project=Trunk xhtml2fo-style-xsl]
|
|
|-
|[http://build.meego.com/package/show?package=xinetd&project=Trunk xinetd]
|
|
|-
|[http://build.meego.com/package/show?package=xinput_calibrator&project=Trunk xinput_calibrator]
|
|
|-
|[http://build.meego.com/package/show?package=xkeyboard-config&project=Trunk xkeyboard-config]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xmlrpc-c&project=Trunk xmlrpc-c]
|
|
|-
|[http://build.meego.com/package/show?package=xmltex&project=Trunk xmltex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=xmlto&project=Trunk xmlto]
|jfding
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-apps&project=Trunk xorg-x11-apps]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-evdev&project=Trunk xorg-x11-drv-evdev]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-evtouch&project=Trunk xorg-x11-drv-evtouch]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-fbdev&project=Trunk xorg-x11-drv-fbdev]
|kad
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-intel&project=Trunk xorg-x11-drv-intel]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-joystick&project=Trunk xorg-x11-drv-joystick]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-keyboard&project=Trunk xorg-x11-drv-keyboard]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-kvm&project=Trunk xorg-x11-drv-kvm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mga&project=Trunk xorg-x11-drv-mga]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mouse&project=Trunk xorg-x11-drv-mouse]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mtev&project=Trunk xorg-x11-drv-mtev]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-omapfb&project=Trunk xorg-x11-drv-omapfb]
|boudra
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-synaptics&project=Trunk xorg-x11-drv-synaptics]
|yanli
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vesa&project=Trunk xorg-x11-drv-vesa]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vmmouse&project=Trunk xorg-x11-drv-vmmouse]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vmware&project=Trunk xorg-x11-drv-vmware]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-void&project=Trunk xorg-x11-drv-void]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-wacom&project=Trunk xorg-x11-drv-wacom]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-filesystem&project=Trunk xorg-x11-filesystem]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-font-utils&project=Trunk xorg-x11-font-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-fonts&project=Trunk xorg-x11-fonts]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-meego-configs&project=Trunk xorg-x11-meego-configs]
|ulf
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-bigreqsproto&project=Trunk xorg-x11-proto-bigreqsproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-compositeproto&project=Trunk xorg-x11-proto-compositeproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-damageproto&project=Trunk xorg-x11-proto-damageproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-dmxproto&project=Trunk xorg-x11-proto-dmxproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-dri2proto&project=Trunk xorg-x11-proto-dri2proto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-evieext&project=Trunk xorg-x11-proto-evieext]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fixesproto&project=Trunk xorg-x11-proto-fixesproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fontcacheproto&project=Trunk xorg-x11-proto-fontcacheproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fontsproto&project=Trunk xorg-x11-proto-fontsproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-glproto&project=Trunk xorg-x11-proto-glproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-inputproto&project=Trunk xorg-x11-proto-inputproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-kbproto&project=Trunk xorg-x11-proto-kbproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-randrproto&project=Trunk xorg-x11-proto-randrproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-recordproto&project=Trunk xorg-x11-proto-recordproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-renderproto&project=Trunk xorg-x11-proto-renderproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-resourceproto&project=Trunk xorg-x11-proto-resourceproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-scrnsaverproto&project=Trunk xorg-x11-proto-scrnsaverproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-trapproto&project=Trunk xorg-x11-proto-trapproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-videoproto&project=Trunk xorg-x11-proto-videoproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xcmiscproto&project=Trunk xorg-x11-proto-xcmiscproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xextproto&project=Trunk xorg-x11-proto-xextproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86bigfontproto&project=Trunk xorg-x11-proto-xf86bigfontproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86dgaproto&project=Trunk xorg-x11-proto-xf86dgaproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86driproto&project=Trunk xorg-x11-proto-xf86driproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86miscproto&project=Trunk xorg-x11-proto-xf86miscproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86rushproto&project=Trunk xorg-x11-proto-xf86rushproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86vidmodeproto&project=Trunk xorg-x11-proto-xf86vidmodeproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xineramaproto&project=Trunk xorg-x11-proto-xineramaproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xproto&project=Trunk xorg-x11-proto-xproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xproxymanagementprotocol&project=Trunk xorg-x11-proto-xproxymanagementprotocol]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-server&project=Trunk xorg-x11-server]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-server-utils&project=Trunk xorg-x11-server-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-twm&project=Trunk xorg-x11-twm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-util-macros&project=Trunk xorg-x11-util-macros]
|pli1,xyl
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils&project=Trunk xorg-x11-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-iceauth&project=Trunk xorg-x11-utils-iceauth]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-rgb&project=Trunk xorg-x11-utils-rgb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-sessreg&project=Trunk xorg-x11-utils-sessreg]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xcmsdb&project=Trunk xorg-x11-utils-xcmsdb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xdpyinfo&project=Trunk xorg-x11-utils-xdpyinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xdriinfo&project=Trunk xorg-x11-utils-xdriinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xev&project=Trunk xorg-x11-utils-xev]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xfd&project=Trunk xorg-x11-utils-xfd]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xfontsel&project=Trunk xorg-x11-utils-xfontsel]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xgamma&project=Trunk xorg-x11-utils-xgamma]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xhost&project=Trunk xorg-x11-utils-xhost]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xinput&project=Trunk xorg-x11-utils-xinput]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsatoms&project=Trunk xorg-x11-utils-xlsatoms]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsclients&project=Trunk xorg-x11-utils-xlsclients]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsfonts&project=Trunk xorg-x11-utils-xlsfonts]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xmodmap&project=Trunk xorg-x11-utils-xmodmap]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xprop&project=Trunk xorg-x11-utils-xprop]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrandr&project=Trunk xorg-x11-utils-xrandr]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrdb&project=Trunk xorg-x11-utils-xrdb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrefresh&project=Trunk xorg-x11-utils-xrefresh]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xset&project=Trunk xorg-x11-utils-xset]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xsetroot&project=Trunk xorg-x11-utils-xsetroot]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xvinfo&project=Trunk xorg-x11-utils-xvinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xwininfo&project=Trunk xorg-x11-utils-xwininfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xauth&project=Trunk xorg-x11-xauth]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xbitmaps&project=Trunk xorg-x11-xbitmaps]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xinit&project=Trunk xorg-x11-xinit]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xkb-utils&project=Trunk xorg-x11-xkb-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xtrans-devel&project=Trunk xorg-x11-xtrans-devel]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xterm&project=Trunk xterm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xz&project=Trunk xz]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=xz-libs-x86&project=Trunk xz-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=yasm&project=Trunk yasm]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=yelp&project=Trunk yelp]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=yum&project=Trunk yum]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=yum-metadata-parser&project=Trunk yum-metadata-parser]
|
|
|-
|[http://build.meego.com/package/show?package=yum-utils&project=Trunk yum-utils]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=zenity&project=Trunk zenity]
|
|
|-
|[http://build.meego.com/package/show?package=zile&project=Trunk zile]
|
|
|-
|[http://build.meego.com/package/show?package=zip&project=Trunk zip]
|yyang,xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=zlib&project=Trunk zlib]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=zlib-x86&project=Trunk zlib-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=zsh&project=Trunk zsh]
|nashif
|
|-
|[http://build.meego.com/package/show?package=zvbi&project=Trunk zvbi]
|
|
|-
|[http://build.meego.com/package/show?package=zypper&project=Trunk zypper]
|xiaoqiang
|devel:packagemanagement
|-
|}

[[Category:Packaging]]

Packaging/Maintainers

2011-04-20T19:07:51Z

Pmccarty: add myself as maintainer for meego-ux-translations

{|border="1"
! Package
! Maintainers (bugowner)
! Development Project
|-

|[http://build.meego.com/package/show?package=ConsoleKit&project=Trunk ConsoleKit]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=FUR&project=Trunk FUR]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=GConf-dbus&project=Trunk GConf-dbus]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=ImageMagick&project=Trunk ImageMagick]
|
|
|-
|[http://build.meego.com/package/show?package=MAKEDEV&project=Trunk MAKEDEV]
|
|
|-
|[http://build.meego.com/package/show?package=ORBit2&project=Trunk ORBit2]
|
|
|-
|[http://build.meego.com/package/show?package=OpenCV&project=Trunk OpenCV]
|
|
|-
|[http://build.meego.com/package/show?package=OpenEXR&project=Trunk OpenEXR]
|
|
|-
|[http://build.meego.com/package/show?package=PackageKit&project=Trunk PackageKit]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=PyOpenGL&project=Trunk PyOpenGL]
|
|
|-
|[http://build.meego.com/package/show?package=PyXML&project=Trunk PyXML]
|
|
|-
|[http://build.meego.com/package/show?package=PyYAML&project=Trunk PyYAML]
|jfding
|
|-
|[http://build.meego.com/package/show?package=SDL&project=Trunk SDL]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_Pango&project=Trunk SDL_Pango]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_gfx&project=Trunk SDL_gfx]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_image&project=Trunk SDL_image]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_mixer&project=Trunk SDL_mixer]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_net&project=Trunk SDL_net]
|
|
|-
|[http://build.meego.com/package/show?package=SDL_ttf&project=Trunk SDL_ttf]
|
|
|-
|[http://build.meego.com/package/show?package=SOAPpy&project=Trunk SOAPpy]
|
|
|-
|[http://build.meego.com/package/show?package=WebKit&project=Trunk WebKit]
|yanli
|
|-
|[http://build.meego.com/package/show?package=WiMAX-Network-Service&project=Trunk WiMAX-Network-Service]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=Xaw3d&project=Trunk Xaw3d]
|
|
|-
|[http://build.meego.com/package/show?package=abiword&project=Trunk abiword]
|
|
|-
|[http://build.meego.com/package/show?package=acct&project=Trunk acct]
|
|
|-
|[http://build.meego.com/package/show?package=acl&project=Trunk acl]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=acpid&project=Trunk acpid]
|
|
|-
|[http://build.meego.com/package/show?package=adns&project=Trunk adns]
|
|
|-
|[http://build.meego.com/package/show?package=aiksaurus&project=Trunk aiksaurus]
|
|
|-
|[http://build.meego.com/package/show?package=alsa-lib&project=Trunk alsa-lib]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=alsa-plugins&project=Trunk alsa-plugins]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=alsa-utils&project=Trunk alsa-utils]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=anerley&project=Trunk anerley]
|rbradford
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=anjuta&project=Trunk anjuta]
|
|
|-
|[http://build.meego.com/package/show?package=anthy&project=Trunk anthy]
|
|
|-
|[http://build.meego.com/package/show?package=apr&project=Trunk apr]
|
|
|-
|[http://build.meego.com/package/show?package=apr-util&project=Trunk apr-util]
|
|
|-
|[http://build.meego.com/package/show?package=aria2&project=Trunk aria2]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=asciidoc&project=Trunk asciidoc]
|
|
|-
|[http://build.meego.com/package/show?package=asio&project=Trunk asio]
|
|
|-
|[http://build.meego.com/package/show?package=aspell&project=Trunk aspell]
|
|
|-
|[http://build.meego.com/package/show?package=aspell-en&project=Trunk aspell-en]
|
|
|-
|[http://build.meego.com/package/show?package=at&project=Trunk at]
|
|
|-
|[http://build.meego.com/package/show?package=at-spi&project=Trunk at-spi]
|
|
|-
|[http://build.meego.com/package/show?package=atk&project=Trunk atk]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=atproxy&project=Trunk atproxy]
|jpfreyen,ulf
|
|-
|[http://build.meego.com/package/show?package=attica&project=Trunk attica]
|boudra
|
|-
|[http://build.meego.com/package/show?package=attr&project=Trunk attr]
|
|
|-
|[http://build.meego.com/package/show?package=audio_management&project=Trunk audio_management]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=audiofile&project=Trunk audiofile]
|
|
|-
|[http://build.meego.com/package/show?package=augeas&project=Trunk augeas]
|
|
|-
|[http://build.meego.com/package/show?package=autoconf&project=Trunk autoconf]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=autoconf213&project=Trunk autoconf213]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=autogen&project=Trunk autogen]
|
|
|-
|[http://build.meego.com/package/show?package=automake&project=Trunk automake]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automake14&project=Trunk automake14]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automake17&project=Trunk automake17]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=automoc4&project=Trunk automoc4]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=autotrace&project=Trunk autotrace]
|
|
|-
|[http://build.meego.com/package/show?package=avahi&project=Trunk avahi]
|
|
|-
|[http://build.meego.com/package/show?package=babl&project=Trunk babl]
|
|
|-
|[http://build.meego.com/package/show?package=baekmuk-ttf-fonts&project=Trunk baekmuk-ttf-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=banshee-1&project=Trunk banshee-1]
|abock
|
|-
|[http://build.meego.com/package/show?package=banshee-1-branding-meego&project=Trunk banshee-1-branding-meego]
|
|
|-
|[http://build.meego.com/package/show?package=basesystem&project=Trunk basesystem]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bash&project=Trunk bash]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=bash-x86&project=Trunk bash-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=bc&project=Trunk bc]
|
|
|-
|[http://build.meego.com/package/show?package=bind&project=Trunk bind]
|jfding
|
|-
|[http://build.meego.com/package/show?package=binutils&project=Trunk binutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bisho&project=Trunk bisho]
|ross
|devel:ux:netbook
|-
|[http://build.meego.com/package/show?package=bison&project=Trunk bison]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bitmap&project=Trunk bitmap]
|
|
|-
|[http://build.meego.com/package/show?package=bitstream-vera-fonts&project=Trunk bitstream-vera-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=bluetooth-ivi&project=Trunk bluetooth-ivi]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=bluez&project=Trunk bluez]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=boardname&project=Trunk boardname]
|auke
|
|-
|[http://build.meego.com/package/show?package=bognor-regis&project=Trunk bognor-regis]
|
|
|-
|[http://build.meego.com/package/show?package=boost&project=Trunk boost]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=bootchart&project=Trunk bootchart]
|auke
|
|-
|[http://build.meego.com/package/show?package=bootstub&project=Trunk bootstub]
|praj
|
|-
|[http://build.meego.com/package/show?package=booty&project=Trunk booty]
|
|
|-
|[http://build.meego.com/package/show?package=brasero&project=Trunk brasero]
|
|
|-
|[http://build.meego.com/package/show?package=btrfs-progs&project=Trunk btrfs-progs]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=bugle&project=Trunk bugle]
|
|
|-
|[http://build.meego.com/package/show?package=build&project=Trunk build]
|nashif
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=build-compare&project=Trunk build-compare]
|nashif
|
|-
|[http://build.meego.com/package/show?package=busybox&project=Trunk busybox]
|
|
|-
|[http://build.meego.com/package/show?package=buteo-mtp&project=Trunk buteo-mtp]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-sync-plugins&project=Trunk buteo-sync-plugins]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-syncfw&project=Trunk buteo-syncfw]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=buteo-syncml&project=Trunk buteo-syncml]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=byacc&project=Trunk byacc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=bzip2&project=Trunk bzip2]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=bzip2-libs-x86&project=Trunk bzip2-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=bzip2-x86&project=Trunk bzip2-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=c-ares&project=Trunk c-ares]
|
|
|-
|[http://build.meego.com/package/show?package=ca-certificates&project=Trunk ca-certificates]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=cabextract&project=Trunk cabextract]
|
|
|-
|[http://build.meego.com/package/show?package=cairo&project=Trunk cairo]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=cairomm&project=Trunk cairomm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=calligra&project=Trunk calligra]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=camera-adaption-layer&project=Trunk camera-adaption-layer]
|ulf
|
|-
|[http://build.meego.com/package/show?package=catdoc&project=Trunk catdoc]
|
|
|-
|[http://build.meego.com/package/show?package=ccache&project=Trunk ccache]
|nashif
|
|-
|[http://build.meego.com/package/show?package=cdrdao&project=Trunk cdrdao]
|
|
|-
|[http://build.meego.com/package/show?package=cdrkit&project=Trunk cdrkit]
|
|
|-
|[http://build.meego.com/package/show?package=cedevicemanager&project=Trunk cedevicemanager]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=cglaunch&project=Trunk cglaunch]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=check&project=Trunk check]
|
|
|-
|[http://build.meego.com/package/show?package=cheese&project=Trunk cheese]
|
|
|-
|[http://build.meego.com/package/show?package=chkconfig&project=Trunk chkconfig]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=chrome-meego-extension&project=Trunk chrome-meego-extension]
|nhu
|
|-
|[http://build.meego.com/package/show?package=chromium&project=Trunk chromium]
|
|devel:browser
|-
|[http://build.meego.com/package/show?package=chrpath&project=Trunk chrpath]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=cjkuni-fonts&project=Trunk cjkuni-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=clean-device&project=Trunk clean-device]
|kedz
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=cloog&project=Trunk cloog]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=clucene&project=Trunk clucene]
|boudra
|
|-
|[http://build.meego.com/package/show?package=clutter&project=Trunk clutter]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-box2d&project=Trunk clutter-box2d]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-gesture&project=Trunk clutter-gesture]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-gst&project=Trunk clutter-gst]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-gtk&project=Trunk clutter-gtk]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=clutter-imcontext&project=Trunk clutter-imcontext]
|rbradford
|devel:clutter
|-
|[http://build.meego.com/package/show?package=cmake&project=Trunk cmake]
|austin,boudra
|
|-
|[http://build.meego.com/package/show?package=cmake-gui&project=Trunk cmake-gui]
|boudra
|
|-
|[http://build.meego.com/package/show?package=commhistory-daemon&project=Trunk commhistory-daemon]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=compat-libstdc++-33&project=Trunk compat-libstdc++-33]
|austin
|
|-
|[http://build.meego.com/package/show?package=compat-telepathy-qt4&project=Trunk compat-telepathy-qt4]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=compface&project=Trunk compface]
|
|
|-
|[http://build.meego.com/package/show?package=comps-extras&project=Trunk comps-extras]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=connman&project=Trunk connman]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=connman-qt&project=Trunk connman-qt]
|kevronx_m_rees
|
|-
|[http://build.meego.com/package/show?package=contacts&project=Trunk contacts]
|
|
|-
|[http://build.meego.com/package/show?package=contactsd&project=Trunk contactsd]
|
|devel:people
|-
|[http://build.meego.com/package/show?package=contextkit&project=Trunk contextkit]
|rusty,lamadon
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=contextkit-maemo&project=Trunk contextkit-maemo]
|rusty,lamadon
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=contextkit-meego&project=Trunk contextkit-meego]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=coreutils&project=Trunk coreutils]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=coreutils-x86&project=Trunk coreutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=corewatcher&project=Trunk corewatcher]
|wdouglas
|
|-
|[http://build.meego.com/package/show?package=corkscrew&project=Trunk corkscrew]
|boudra
|
|-
|[http://build.meego.com/package/show?package=cpio&project=Trunk cpio]
|yanli
|
|-
|[http://build.meego.com/package/show?package=cppcheck&project=Trunk cppcheck]
|arjan
|
|-
|[http://build.meego.com/package/show?package=cppunit&project=Trunk cppunit]
|
|
|-
|[http://build.meego.com/package/show?package=crda&project=Trunk crda]
|
|
|-
|[http://build.meego.com/package/show?package=createrepo&project=Trunk createrepo]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=cronie&project=Trunk cronie]
|yyang
|
|-
|[http://build.meego.com/package/show?package=crontabs&project=Trunk crontabs]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-binutils&project=Trunk cross-armv5tel-binutils]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-binutils-accel&project=Trunk cross-armv5tel-binutils-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-gcc&project=Trunk cross-armv5tel-gcc]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv5tel-gcc-accel&project=Trunk cross-armv5tel-gcc-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-binutils&project=Trunk cross-armv7hl-binutils]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-binutils-accel&project=Trunk cross-armv7hl-binutils-accel]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-gcc&project=Trunk cross-armv7hl-gcc]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7hl-gcc-accel&project=Trunk cross-armv7hl-gcc-accel]
|
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-binutils&project=Trunk cross-armv7l-binutils]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-binutils-accel&project=Trunk cross-armv7l-binutils-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-gcc&project=Trunk cross-armv7l-gcc]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-gcc-accel&project=Trunk cross-armv7l-gcc-accel]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=cross-armv7l-platformfile&project=Trunk cross-armv7l-platformfile]
|cvm
|
|-
|[http://build.meego.com/package/show?package=cross-armv7tnhl-platformfile&project=Trunk cross-armv7tnhl-platformfile]
|cvm
|
|-
|[http://build.meego.com/package/show?package=cryptsetup-luks&project=Trunk cryptsetup-luks]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=cscope&project=Trunk cscope]
|
|
|-
|[http://build.meego.com/package/show?package=ctags&project=Trunk ctags]
|
|
|-
|[http://build.meego.com/package/show?package=ctdb&project=Trunk ctdb]
|
|
|-
|[http://build.meego.com/package/show?package=cups&project=Trunk cups]
|itachi
|
|-
|[http://build.meego.com/package/show?package=curl&project=Trunk curl]
|
|
|-
|[http://build.meego.com/package/show?package=cvs&project=Trunk cvs]
|
|
|-
|[http://build.meego.com/package/show?package=cyrus-sasl&project=Trunk cyrus-sasl]
|
|
|-
|[http://build.meego.com/package/show?package=d-feet&project=Trunk d-feet]
|
|
|-
|[http://build.meego.com/package/show?package=db4&project=Trunk db4]
|yyin2
|devel:base
|-
|[http://build.meego.com/package/show?package=db4-x86&project=Trunk db4-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=dblatex&project=Trunk dblatex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=dbus&project=Trunk dbus]
|huaxu
|devel:base
|-
|[http://build.meego.com/package/show?package=dbus-glib&project=Trunk dbus-glib]
|huaxu
|
|-
|[http://build.meego.com/package/show?package=dbus-python&project=Trunk dbus-python]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=dejagnu&project=Trunk dejagnu]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=dejavu-fonts&project=Trunk dejavu-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=deltarpm&project=Trunk deltarpm]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=desktop-backgrounds&project=Trunk desktop-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=desktop-file-utils&project=Trunk desktop-file-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=dev86&project=Trunk dev86]
|
|
|-
|[http://build.meego.com/package/show?package=devhelp&project=Trunk devhelp]
|jfding
|devel:gnome
|-
|[http://build.meego.com/package/show?package=device-mapper&project=Trunk device-mapper]
|yyang
|
|-
|[http://build.meego.com/package/show?package=device-mapper-multipath&project=Trunk device-mapper-multipath]
|yyang
|
|-
|[http://build.meego.com/package/show?package=dia&project=Trunk dia]
|
|
|-
|[http://build.meego.com/package/show?package=dialog&project=Trunk dialog]
|
|
|-
|[http://build.meego.com/package/show?package=diffstat&project=Trunk diffstat]
|yyang
|
|-
|[http://build.meego.com/package/show?package=diffutils&project=Trunk diffutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=diffutils-x86&project=Trunk diffutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=distcc&project=Trunk distcc]
|
|
|-
|[http://build.meego.com/package/show?package=djvulibre&project=Trunk djvulibre]
|
|
|-
|[http://build.meego.com/package/show?package=dmidecode&project=Trunk dmidecode]
|
|
|-
|[http://build.meego.com/package/show?package=dnsmasq&project=Trunk dnsmasq]
|martin
|
|-
|[http://build.meego.com/package/show?package=docbook-dtds&project=Trunk docbook-dtds]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-style-dsssl&project=Trunk docbook-style-dsssl]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-style-xsl&project=Trunk docbook-style-xsl]
|
|
|-
|[http://build.meego.com/package/show?package=docbook-utils&project=Trunk docbook-utils]
|
|
|-
|[http://build.meego.com/package/show?package=dos2unix&project=Trunk dos2unix]
|
|
|-
|[http://build.meego.com/package/show?package=dosfstools&project=Trunk dosfstools]
|
|
|-
|[http://build.meego.com/package/show?package=dotconf&project=Trunk dotconf]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=doxygen&project=Trunk doxygen]
|
|
|-
|[http://build.meego.com/package/show?package=doxygen-x86&project=Trunk doxygen-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=doxymacs&project=Trunk doxymacs]
|
|
|-
|[http://build.meego.com/package/show?package=driconf&project=Trunk driconf]
|xyl
|
|-
|[http://build.meego.com/package/show?package=droid-fonts&project=Trunk droid-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=dropbear&project=Trunk dropbear]
|austin
|
|-
|[http://build.meego.com/package/show?package=dsme&project=Trunk dsme]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=dsp-tools&project=Trunk dsp-tools]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=dvd+rw-tools&project=Trunk dvd+rw-tools]
|
|
|-
|[http://build.meego.com/package/show?package=dvipdfm&project=Trunk dvipdfm]
|
|
|-
|[http://build.meego.com/package/show?package=dvipdfmx&project=Trunk dvipdfmx]
|yanli
|
|-
|[http://build.meego.com/package/show?package=dvipng&project=Trunk dvipng]
|
|
|-
|[http://build.meego.com/package/show?package=e2fsprogs&project=Trunk e2fsprogs]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=eat&project=Trunk eat]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=ecryptfs-utils&project=Trunk ecryptfs-utils]
|yanli
|
|-
|[http://build.meego.com/package/show?package=ed&project=Trunk ed]
|yyang
|
|-
|[http://build.meego.com/package/show?package=eggdbus&project=Trunk eggdbus]
|
|
|-
|[http://build.meego.com/package/show?package=eject&project=Trunk eject]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=elfutils&project=Trunk elfutils]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=elfutils-libelf-x86&project=Trunk elfutils-libelf-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=elfutils-libs-x86&project=Trunk elfutils-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=elfutils-x86&project=Trunk elfutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=emacs&project=Trunk emacs]
|
|
|-
|[http://build.meego.com/package/show?package=empathy&project=Trunk empathy]
|
|
|-
|[http://build.meego.com/package/show?package=enchant&project=Trunk enchant]
|
|
|-
|[http://build.meego.com/package/show?package=enscript&project=Trunk enscript]
|
|
|-
|[http://build.meego.com/package/show?package=eog&project=Trunk eog]
|
|
|-
|[http://build.meego.com/package/show?package=eog-plugins&project=Trunk eog-plugins]
|
|
|-
|[http://build.meego.com/package/show?package=eom&project=Trunk eom]
|
|
|-
|[http://build.meego.com/package/show?package=epydoc&project=Trunk epydoc]
|
|
|-
|[http://build.meego.com/package/show?package=esound&project=Trunk esound]
|
|
|-
|[http://build.meego.com/package/show?package=etherboot&project=Trunk etherboot]
|
|
|-
|[http://build.meego.com/package/show?package=ethtool&project=Trunk ethtool]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=evince&project=Trunk evince]
|
|
|-
|[http://build.meego.com/package/show?package=evolution&project=Trunk evolution]
|ross
|
|-
|[http://build.meego.com/package/show?package=evolution-data-server&project=Trunk evolution-data-server]
|
|
|-
|[http://build.meego.com/package/show?package=evtest&project=Trunk evtest]
|ulf
|
|-
|[http://build.meego.com/package/show?package=exempi&project=Trunk exempi]
|
|
|-
|[http://build.meego.com/package/show?package=exiv2&project=Trunk exiv2]
|
|
|-
|[http://build.meego.com/package/show?package=expat&project=Trunk expat]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=expect&project=Trunk expect]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=fakechroot&project=Trunk fakechroot]
|yyang
|
|-
|[http://build.meego.com/package/show?package=fakeroot&project=Trunk fakeroot]
|
|
|-
|[http://build.meego.com/package/show?package=farsight2&project=Trunk farsight2]
|
|
|-
|[http://build.meego.com/package/show?package=fastinit&project=Trunk fastinit]
|
|
|-
|[http://build.meego.com/package/show?package=fastjar&project=Trunk fastjar]
|austin
|
|-
|[http://build.meego.com/package/show?package=fdupes&project=Trunk fdupes]
|nashif
|
|-
|[http://build.meego.com/package/show?package=fdupes-x86&project=Trunk fdupes-x86]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=fennec-qt&project=Trunk fennec-qt]
|logoel
|
|-
|[http://build.meego.com/package/show?package=fennec-qt-branding-meego&project=Trunk fennec-qt-branding-meego]
|
|
|-
|[http://build.meego.com/package/show?package=fennec-taskswitcher-extension&project=Trunk fennec-taskswitcher-extension]
|logoel
|
|-
|[http://build.meego.com/package/show?package=festival&project=Trunk festival]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=festival-freebsoft-utils&project=Trunk festival-freebsoft-utils]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=file&project=Trunk file]
|
|
|-
|[http://build.meego.com/package/show?package=file-libs-x86&project=Trunk file-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=file-roller&project=Trunk file-roller]
|
|
|-
|[http://build.meego.com/package/show?package=file-x86&project=Trunk file-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=filesystem&project=Trunk filesystem]
|
|
|-
|[http://build.meego.com/package/show?package=findutils&project=Trunk findutils]
|yanli
|
|-
|[http://build.meego.com/package/show?package=findutils-x86&project=Trunk findutils-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=firstboot&project=Trunk firstboot]
|vivian
|
|-
|[http://build.meego.com/package/show?package=flac&project=Trunk flac]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=flex&project=Trunk flex]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=fontconfig&project=Trunk fontconfig]
|yanli
|
|-
|[http://build.meego.com/package/show?package=fontforge&project=Trunk fontforge]
|yanli
|
|-
|[http://build.meego.com/package/show?package=fontpackages&project=Trunk fontpackages]
|yanli
|
|-
|[http://build.meego.com/package/show?package=foomatic&project=Trunk foomatic]
|
|
|-
|[http://build.meego.com/package/show?package=foomatic-db&project=Trunk foomatic-db]
|
|
|-
|[http://build.meego.com/package/show?package=fortune-mod&project=Trunk fortune-mod]
|ulf
|
|-
|[http://build.meego.com/package/show?package=fprintd&project=Trunk fprintd]
|
|
|-
|[http://build.meego.com/package/show?package=freeglut&project=Trunk freeglut]
|xyl
|
|-
|[http://build.meego.com/package/show?package=freepats&project=Trunk freepats]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=freetype&project=Trunk freetype]
|
|
|-
|[http://build.meego.com/package/show?package=fribidi&project=Trunk fribidi]
|
|
|-
|[http://build.meego.com/package/show?package=frozen-bubble&project=Trunk frozen-bubble]
|
|
|-
|[http://build.meego.com/package/show?package=fslint&project=Trunk fslint]
|jiachenghu
|
|-
|[http://build.meego.com/package/show?package=fuse&project=Trunk fuse]
|
|
|-
|[http://build.meego.com/package/show?package=fuse-sshfs&project=Trunk fuse-sshfs]
|
|
|-
|[http://build.meego.com/package/show?package=fvkbd&project=Trunk fvkbd]
|
|
|-
|[http://build.meego.com/package/show?package=fw-update&project=Trunk fw-update]
|praj
|
|-
|[http://build.meego.com/package/show?package=gamin&project=Trunk gamin]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=gammu&project=Trunk gammu]
|boudra
|
|-
|[http://build.meego.com/package/show?package=garage-client-services&project=Trunk garage-client-services]
|jackiewu
|
|-
|[http://build.meego.com/package/show?package=garage-netbook-ui&project=Trunk garage-netbook-ui]
|jackiewu
|
|-
|[http://build.meego.com/package/show?package=gawk&project=Trunk gawk]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gawk-x86&project=Trunk gawk-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=gc&project=Trunk gc]
|
|
|-
|[http://build.meego.com/package/show?package=gcalctool&project=Trunk gcalctool]
|
|
|-
|[http://build.meego.com/package/show?package=gcc&project=Trunk gcc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gcc-cross&project=Trunk gcc-cross]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=gconf-editor&project=Trunk gconf-editor]
|
|
|-
|[http://build.meego.com/package/show?package=gd&project=Trunk gd]
|
|
|-
|[http://build.meego.com/package/show?package=gdb&project=Trunk gdb]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gdbm&project=Trunk gdbm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gdu-nautilus-extension&project=Trunk gdu-nautilus-extension]
|
|
|-
|[http://build.meego.com/package/show?package=gedit&project=Trunk gedit]
|
|
|-
|[http://build.meego.com/package/show?package=gegl&project=Trunk gegl]
|
|
|-
|[http://build.meego.com/package/show?package=generic-backgrounds&project=Trunk generic-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=generic-logos&project=Trunk generic-logos]
|
|
|-
|[http://build.meego.com/package/show?package=geoclue&project=Trunk geoclue]
|
|
|-
|[http://build.meego.com/package/show?package=gettext&project=Trunk gettext]
|
|
|-
|[http://build.meego.com/package/show?package=ghostscript&project=Trunk ghostscript]
|itachi
|
|-
|[http://build.meego.com/package/show?package=ghostscript-fonts&project=Trunk ghostscript-fonts]
|itachi
|
|-
|[http://build.meego.com/package/show?package=giflib&project=Trunk giflib]
|
|
|-
|[http://build.meego.com/package/show?package=gimp&project=Trunk gimp]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=git&project=Trunk git]
|
|
|-
|[http://build.meego.com/package/show?package=glade3&project=Trunk glade3]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gles-libs&project=Trunk gles-libs]
|boudra
|
|-
|[http://build.meego.com/package/show?package=glew&project=Trunk glew]
|
|
|-
|[http://build.meego.com/package/show?package=glib2&project=Trunk glib2]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=glibc&project=Trunk glibc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=glibc-arm&project=Trunk glibc-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-devel-arm&project=Trunk glibc-devel-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-headers-arm&project=Trunk glibc-headers-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=glibc-x86&project=Trunk glibc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=glibmm&project=Trunk glibmm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gmime&project=Trunk gmime]
|
|
|-
|[http://build.meego.com/package/show?package=gmp&project=Trunk gmp]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=gmp-x86&project=Trunk gmp-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=gnet2&project=Trunk gnet2]
|
|
|-
|[http://build.meego.com/package/show?package=gnome-bluetooth&project=Trunk gnome-bluetooth]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-common&project=Trunk gnome-common]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-control-center-netbook&project=Trunk gnome-control-center-netbook]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-desktop&project=Trunk gnome-desktop]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-disk-utility&project=Trunk gnome-disk-utility]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-doc-utils&project=Trunk gnome-doc-utils]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-games&project=Trunk gnome-games]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-icon-theme&project=Trunk gnome-icon-theme]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-keyring&project=Trunk gnome-keyring]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-media&project=Trunk gnome-media]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-menus&project=Trunk gnome-menus]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-mime-data&project=Trunk gnome-mime-data]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-packagekit&project=Trunk gnome-packagekit]
|quanxianwang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=gnome-panel&project=Trunk gnome-panel]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-python2&project=Trunk gnome-python2]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-python2-desktop&project=Trunk gnome-python2-desktop]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-screensaver&project=Trunk gnome-screensaver]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-session&project=Trunk gnome-session]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-settings-daemon&project=Trunk gnome-settings-daemon]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-sharp2&project=Trunk gnome-sharp2]
|mmeeks
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-terminal&project=Trunk gnome-terminal]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-themes&project=Trunk gnome-themes]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-user-docs&project=Trunk gnome-user-docs]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-user-share&project=Trunk gnome-user-share]
|ross
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-utils&project=Trunk gnome-utils]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnome-vfs2&project=Trunk gnome-vfs2]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gnonlin&project=Trunk gnonlin]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gnu-efi&project=Trunk gnu-efi]
|
|
|-
|[http://build.meego.com/package/show?package=gnuchess&project=Trunk gnuchess]
|
|
|-
|[http://build.meego.com/package/show?package=gnumeric&project=Trunk gnumeric]
|
|
|-
|[http://build.meego.com/package/show?package=gnupg&project=Trunk gnupg]
|
|
|-
|[http://build.meego.com/package/show?package=gnupg2&project=Trunk gnupg2]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gnutls&project=Trunk gnutls]
|qzhao9,yanli
|devel:security
|-
|[http://build.meego.com/package/show?package=goffice&project=Trunk goffice]
|
|
|-
|[http://build.meego.com/package/show?package=google-gadgets&project=Trunk google-gadgets]
|wwang29
|
|-
|[http://build.meego.com/package/show?package=gperf&project=Trunk gperf]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gpgme&project=Trunk gpgme]
|
|
|-
|[http://build.meego.com/package/show?package=gphotofs&project=Trunk gphotofs]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=gpsbabel&project=Trunk gpsbabel]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gpsd&project=Trunk gpsd]
|
|
|-
|[http://build.meego.com/package/show?package=gpsdrive&project=Trunk gpsdrive]
|
|
|-
|[http://build.meego.com/package/show?package=graphviz&project=Trunk graphviz]
|
|
|-
|[http://build.meego.com/package/show?package=grep&project=Trunk grep]
|yanli
|
|-
|[http://build.meego.com/package/show?package=grilo&project=Trunk grilo]
|
|
|-
|[http://build.meego.com/package/show?package=grilo-plugins&project=Trunk grilo-plugins]
|
|
|-
|[http://build.meego.com/package/show?package=grisbi&project=Trunk grisbi]
|
|
|-
|[http://build.meego.com/package/show?package=groff&project=Trunk groff]
|
|
|-
|[http://build.meego.com/package/show?package=grub&project=Trunk grub]
|
|
|-
|[http://build.meego.com/package/show?package=grubby&project=Trunk grubby]
|yyang
|
|-
|[http://build.meego.com/package/show?package=gsl&project=Trunk gsl]
|rolla
|
|-
|[http://build.meego.com/package/show?package=gsm&project=Trunk gsm]
|
|
|-
|[http://build.meego.com/package/show?package=gssdp&project=Trunk gssdp]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gst-dsp&project=Trunk gst-dsp]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-bad-free&project=Trunk gst-plugins-bad-free]
|bgao1,lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-base&project=Trunk gst-plugins-base]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-camera&project=Trunk gst-plugins-camera]
|vivian
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-dvbsub&project=Trunk gst-plugins-dvbsub]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-farsight&project=Trunk gst-plugins-farsight]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-flumpegdemux&project=Trunk gst-plugins-flumpegdemux]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-good&project=Trunk gst-plugins-good]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-plugins-teletext&project=Trunk gst-plugins-teletext]
|
|
|-
|[http://build.meego.com/package/show?package=gst-plugins-va&project=Trunk gst-plugins-va]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gst-v4l2-camsrc&project=Trunk gst-v4l2-camsrc]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gst-vabuffer&project=Trunk gst-vabuffer]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gstreamer&project=Trunk gstreamer]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=gstreamer-editing-services&project=Trunk gstreamer-editing-services]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gstreamer-python&project=Trunk gstreamer-python]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gthumb&project=Trunk gthumb]
|
|
|-
|[http://build.meego.com/package/show?package=gtk-doc&project=Trunk gtk-doc]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtk-nodoka-engine&project=Trunk gtk-nodoka-engine]
|
|
|-
|[http://build.meego.com/package/show?package=gtk-sharp2&project=Trunk gtk-sharp2]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=gtk2&project=Trunk gtk2]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gtk2-engines&project=Trunk gtk2-engines]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtkglext&project=Trunk gtkglext]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtkhtml3&project=Trunk gtkhtml3]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=gtkmathview&project=Trunk gtkmathview]
|
|
|-
|[http://build.meego.com/package/show?package=gtkmm&project=Trunk gtkmm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=gtksourceview2&project=Trunk gtksourceview2]
|
|
|-
|[http://build.meego.com/package/show?package=gtkspell&project=Trunk gtkspell]
|
|
|-
|[http://build.meego.com/package/show?package=guile&project=Trunk guile]
|
|
|-
|[http://build.meego.com/package/show?package=gupnp&project=Trunk gupnp]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-av&project=Trunk gupnp-av]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-dlna&project=Trunk gupnp-dlna]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=gupnp-igd&project=Trunk gupnp-igd]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-tools&project=Trunk gupnp-tools]
|
|
|-
|[http://build.meego.com/package/show?package=gupnp-ui&project=Trunk gupnp-ui]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gupnp-vala&project=Trunk gupnp-vala]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=gvfs&project=Trunk gvfs]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=gwenhywfar&project=Trunk gwenhywfar]
|
|
|-
|[http://build.meego.com/package/show?package=gypsy&project=Trunk gypsy]
|
|
|-
|[http://build.meego.com/package/show?package=gzip&project=Trunk gzip]
|yanli
|
|-
|[http://build.meego.com/package/show?package=gzip-x86&project=Trunk gzip-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=hardlink&project=Trunk hardlink]
|yyang
|
|-
|[http://build.meego.com/package/show?package=help2man&project=Trunk help2man]
|
|
|-
|[http://build.meego.com/package/show?package=hfdialer&project=Trunk hfdialer]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=hfdialer-branding-meego&project=Trunk hfdialer-branding-meego]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=hfp&project=Trunk hfp]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=hicolor-icon-theme&project=Trunk hicolor-icon-theme]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=html2ps&project=Trunk html2ps]
|
|
|-
|[http://build.meego.com/package/show?package=hunspell&project=Trunk hunspell]
|
|
|-
|[http://build.meego.com/package/show?package=hunspell-en&project=Trunk hunspell-en]
|
|
|-
|[http://build.meego.com/package/show?package=hwdata&project=Trunk hwdata]
|
|
|-
|[http://build.meego.com/package/show?package=i2c-tools&project=Trunk i2c-tools]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=iasl&project=Trunk iasl]
|
|
|-
|[http://build.meego.com/package/show?package=icon-naming-utils&project=Trunk icon-naming-utils]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=icu&project=Trunk icu]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=ilmbase&project=Trunk ilmbase]
|
|
|-
|[http://build.meego.com/package/show?package=image-configurations&project=Trunk image-configurations]
|nashif
|
|-
|[http://build.meego.com/package/show?package=image-manager&project=Trunk image-manager]
|yyang
|
|-
|[http://build.meego.com/package/show?package=imake&project=Trunk imake]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=indent&project=Trunk indent]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=inkscape&project=Trunk inkscape]
|
|
|-
|[http://build.meego.com/package/show?package=inotify-tools&project=Trunk inotify-tools]
|
|
|-
|[http://build.meego.com/package/show?package=installer&project=Trunk installer]
|vivian
|
|-
|[http://build.meego.com/package/show?package=installer-shell&project=Trunk installer-shell]
|vivian
|
|-
|[http://build.meego.com/package/show?package=intel-gpu-tools&project=Trunk intel-gpu-tools]
|pli1,xyl
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=intltool&project=Trunk intltool]
|
|
|-
|[http://build.meego.com/package/show?package=iproute&project=Trunk iproute]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iptables&project=Trunk iptables]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iputils&project=Trunk iputils]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=iso-codes&project=Trunk iso-codes]
|
|
|-
|[http://build.meego.com/package/show?package=isomd5sum&project=Trunk isomd5sum]
|yyang
|
|-
|[http://build.meego.com/package/show?package=ividesktop&project=Trunk ividesktop]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=ivihome&project=Trunk ivihome]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=iw&project=Trunk iw]
|
|
|-
|[http://build.meego.com/package/show?package=jadetex&project=Trunk jadetex]
|
|
|-
|[http://build.meego.com/package/show?package=jana&project=Trunk jana]
|
|
|-
|[http://build.meego.com/package/show?package=jasper&project=Trunk jasper]
|
|
|-
|[http://build.meego.com/package/show?package=joe&project=Trunk joe]
|
|
|-
|[http://build.meego.com/package/show?package=joystick&project=Trunk joystick]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=json-c&project=Trunk json-c]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=json-glib&project=Trunk json-glib]
|
|
|-
|[http://build.meego.com/package/show?package=kasumi&project=Trunk kasumi]
|
|
|-
|[http://build.meego.com/package/show?package=kbd&project=Trunk kbd]
|
|
|-
|[http://build.meego.com/package/show?package=kcalcore&project=Trunk kcalcore]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=kde-mobile&project=Trunk kde-mobile]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=kernel&project=Trunk kernel]
|
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-connext&project=Trunk kernel-adaptation-connext]
|
|
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-intel-automotive&project=Trunk kernel-adaptation-intel-automotive]
|qi
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-medfield&project=Trunk kernel-adaptation-medfield]
|ldmai
|
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-mrst&project=Trunk kernel-adaptation-mrst]
|arjan
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-n900&project=Trunk kernel-adaptation-n900]
|ikoskine
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=kernel-adaptation-oaktrail&project=Trunk kernel-adaptation-oaktrail]
|kai
|devel:kernel
|-
|[http://build.meego.com/package/show?package=kernel-headers&project=Trunk kernel-headers]
|arjan
|
|-
|[http://build.meego.com/package/show?package=kernel-headers-arm&project=Trunk kernel-headers-arm]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=kexec-tools&project=Trunk kexec-tools]
|apalande
|
|-
|[http://build.meego.com/package/show?package=keycodes-setup&project=Trunk keycodes-setup]
|ulf
|
|-
|[http://build.meego.com/package/show?package=keyutils&project=Trunk keyutils]
|
|
|-
|[http://build.meego.com/package/show?package=kickstarter&project=Trunk kickstarter]
|nashif
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=kmod-virtiogl&project=Trunk kmod-virtiogl]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=krb5&project=Trunk krb5]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=ladspa&project=Trunk ladspa]
|
|
|-
|[http://build.meego.com/package/show?package=lapack&project=Trunk lapack]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=latencytop&project=Trunk latencytop]
|arjan
|
|-
|[http://build.meego.com/package/show?package=latex2html&project=Trunk latex2html]
|
|
|-
|[http://build.meego.com/package/show?package=lcms&project=Trunk lcms]
|
|
|-
|[http://build.meego.com/package/show?package=less&project=Trunk less]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=lftp&project=Trunk lftp]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=libCI&project=Trunk libCI]
|ulf
|
|-
|[http://build.meego.com/package/show?package=libICE&project=Trunk libICE]
|
|
|-
|[http://build.meego.com/package/show?package=libIDL&project=Trunk libIDL]
|
|
|-
|[http://build.meego.com/package/show?package=libSM&project=Trunk libSM]
|
|
|-
|[http://build.meego.com/package/show?package=libX11&project=Trunk libX11]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXScrnSaver&project=Trunk libXScrnSaver]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXTrap&project=Trunk libXTrap]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXau&project=Trunk libXau]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXaw&project=Trunk libXaw]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXcomposite&project=Trunk libXcomposite]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXcursor&project=Trunk libXcursor]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXdamage&project=Trunk libXdamage]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXdmcp&project=Trunk libXdmcp]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXevie&project=Trunk libXevie]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXext&project=Trunk libXext]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXfixes&project=Trunk libXfixes]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXfont&project=Trunk libXfont]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXfontcache&project=Trunk libXfontcache]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXft&project=Trunk libXft]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXi&project=Trunk libXi]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXinerama&project=Trunk libXinerama]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXmu&project=Trunk libXmu]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXpm&project=Trunk libXpm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXrandr&project=Trunk libXrandr]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXrender&project=Trunk libXrender]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXres&project=Trunk libXres]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXt&project=Trunk libXt]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXtst&project=Trunk libXtst]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libXv&project=Trunk libXv]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXvMC&project=Trunk libXvMC]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXxf86dga&project=Trunk libXxf86dga]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXxf86misc&project=Trunk libXxf86misc]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libXxf86vm&project=Trunk libXxf86vm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libaccounts-glib&project=Trunk libaccounts-glib]
|bwachter,pcapriotti
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libaccounts-qt&project=Trunk libaccounts-qt]
|bwachter,pcapriotti
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libaccounts-ui&project=Trunk libaccounts-ui]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libacl-x86&project=Trunk libacl-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libao&project=Trunk libao]
|
|
|-
|[http://build.meego.com/package/show?package=libarchive&project=Trunk libarchive]
|
|
|-
|[http://build.meego.com/package/show?package=libart_lgpl&project=Trunk libart_lgpl]
|
|
|-
|[http://build.meego.com/package/show?package=libassuan&project=Trunk libassuan]
|
|
|-
|[http://build.meego.com/package/show?package=libasyncns&project=Trunk libasyncns]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libatasmart&project=Trunk libatasmart]
|
|
|-
|[http://build.meego.com/package/show?package=libatomic_ops&project=Trunk libatomic_ops]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=libattr-x86&project=Trunk libattr-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libbonobo&project=Trunk libbonobo]
|
|
|-
|[http://build.meego.com/package/show?package=libbonoboui&project=Trunk libbonoboui]
|
|
|-
|[http://build.meego.com/package/show?package=libburn&project=Trunk libburn]
|
|
|-
|[http://build.meego.com/package/show?package=libcanberra&project=Trunk libcanberra]
|vivian
|
|-
|[http://build.meego.com/package/show?package=libcap&project=Trunk libcap]
|
|
|-
|[http://build.meego.com/package/show?package=libcap-ng&project=Trunk libcap-ng]
|
|
|-
|[http://build.meego.com/package/show?package=libcap-x86&project=Trunk libcap-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libchamplain&project=Trunk libchamplain]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=libchewing&project=Trunk libchewing]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libcmtspeech-ifx&project=Trunk libcmtspeech-ifx]
|vivian
|
|-
|[http://build.meego.com/package/show?package=libcmtspeechdata&project=Trunk libcmtspeechdata]
|
|
|-
|[http://build.meego.com/package/show?package=libcommhistory&project=Trunk libcommhistory]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libcontentaction&project=Trunk libcontentaction]
|maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=libcqpid&project=Trunk libcqpid]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=libcreds3&project=Trunk libcreds3]
|peter,rrware
|
|-
|[http://build.meego.com/package/show?package=libcroco&project=Trunk libcroco]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libdaemon&project=Trunk libdaemon]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libdbus-c++&project=Trunk libdbus-c++]
|huaxu
|
|-
|[http://build.meego.com/package/show?package=libdiscid&project=Trunk libdiscid]
|
|
|-
|[http://build.meego.com/package/show?package=libdmx&project=Trunk libdmx]
|
|
|-
|[http://build.meego.com/package/show?package=libdres&project=Trunk libdres]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libdrm&project=Trunk libdrm]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=libdsme&project=Trunk libdsme]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libedit&project=Trunk libedit]
|
|
|-
|[http://build.meego.com/package/show?package=libeigen2&project=Trunk libeigen2]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=libenca&project=Trunk libenca]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=liberation-fonts&project=Trunk liberation-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=libevent&project=Trunk libevent]
|
|
|-
|[http://build.meego.com/package/show?package=libexif&project=Trunk libexif]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libfakekey&project=Trunk libfakekey]
|
|
|-
|[http://build.meego.com/package/show?package=libffi&project=Trunk libffi]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libfontenc&project=Trunk libfontenc]
|yanli
|
|-
|[http://build.meego.com/package/show?package=libfprint&project=Trunk libfprint]
|
|
|-
|[http://build.meego.com/package/show?package=libgail-gnome&project=Trunk libgail-gnome]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgcc-x86&project=Trunk libgcc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=libgcrypt&project=Trunk libgcrypt]
|
|
|-
|[http://build.meego.com/package/show?package=libgda&project=Trunk libgda]
|
|
|-
|[http://build.meego.com/package/show?package=libgdata&project=Trunk libgdata]
|daihan
|
|-
|[http://build.meego.com/package/show?package=libgdbus&project=Trunk libgdbus]
|
|
|-
|[http://build.meego.com/package/show?package=libgdiplus0&project=Trunk libgdiplus0]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=libgdl&project=Trunk libgdl]
|
|
|-
|[http://build.meego.com/package/show?package=libgee&project=Trunk libgee]
|
|
|-
|[http://build.meego.com/package/show?package=libggz&project=Trunk libggz]
|
|
|-
|[http://build.meego.com/package/show?package=libglade2&project=Trunk libglade2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libglademm&project=Trunk libglademm]
|
|
|-
|[http://build.meego.com/package/show?package=libgnome&project=Trunk libgnome]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnome-keyring&project=Trunk libgnome-keyring]
|xiaoqiang,quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomecanvas&project=Trunk libgnomecanvas]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomecups&project=Trunk libgnomecups]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomekbd&project=Trunk libgnomekbd]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomeprint22&project=Trunk libgnomeprint22]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomeprintui22&project=Trunk libgnomeprintui22]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgnomeui&project=Trunk libgnomeui]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libgpg-error&project=Trunk libgpg-error]
|
|
|-
|[http://build.meego.com/package/show?package=libgphoto2&project=Trunk libgphoto2]
|
|
|-
|[http://build.meego.com/package/show?package=libgsf&project=Trunk libgsf]
|
|
|-
|[http://build.meego.com/package/show?package=libgtop2&project=Trunk libgtop2]
|
|
|-
|[http://build.meego.com/package/show?package=libgweather&project=Trunk libgweather]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libhangul&project=Trunk libhangul]
|
|
|-
|[http://build.meego.com/package/show?package=libical&project=Trunk libical]
|boudra
|
|-
|[http://build.meego.com/package/show?package=libid3tag&project=Trunk libid3tag]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libidn&project=Trunk libidn]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libiodata&project=Trunk libiodata]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libiphb&project=Trunk libiphb]
|
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libiptcdata&project=Trunk libiptcdata]
|zivchang
|
|-
|[http://build.meego.com/package/show?package=libisofs&project=Trunk libisofs]
|
|
|-
|[http://build.meego.com/package/show?package=libjingle&project=Trunk libjingle]
|
|
|-
|[http://build.meego.com/package/show?package=libjpeg&project=Trunk libjpeg]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libksba&project=Trunk libksba]
|yanli
|
|-
|[http://build.meego.com/package/show?package=liblua-x86&project=Trunk liblua-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libmatchbox&project=Trunk libmatchbox]
|
|
|-
|[http://build.meego.com/package/show?package=libmeegochat&project=Trunk libmeegochat]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libmeegotouch&project=Trunk libmeegotouch]
|msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libmikmod&project=Trunk libmikmod]
|
|
|-
|[http://build.meego.com/package/show?package=libmlocknice&project=Trunk libmlocknice]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=libmng&project=Trunk libmng]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libmp4v2&project=Trunk libmp4v2]
|
|
|-
|[http://build.meego.com/package/show?package=libmtp&project=Trunk libmtp]
|
|
|-
|[http://build.meego.com/package/show?package=libngf&project=Trunk libngf]
|mantyharju
|
|-
|[http://build.meego.com/package/show?package=libnice&project=Trunk libnice]
|
|
|-
|[http://build.meego.com/package/show?package=libnl&project=Trunk libnl]
|
|
|-
|[http://build.meego.com/package/show?package=libnotify&project=Trunk libnotify]
|
|devel:gnome
|-
|[http://build.meego.com/package/show?package=libofono-qt&project=Trunk libofono-qt]
|sbryan,boudra
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=libofx&project=Trunk libofx]
|
|
|-
|[http://build.meego.com/package/show?package=libogg&project=Trunk libogg]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=liboil&project=Trunk liboil]
|
|
|-
|[http://build.meego.com/package/show?package=libopenraw&project=Trunk libopenraw]
|
|
|-
|[http://build.meego.com/package/show?package=libopensync&project=Trunk libopensync]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libopensync-plugin-vformat&project=Trunk libopensync-plugin-vformat]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libpaper&project=Trunk libpaper]
|
|
|-
|[http://build.meego.com/package/show?package=libpcap&project=Trunk libpcap]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=libpciaccess&project=Trunk libpciaccess]
|
|
|-
|[http://build.meego.com/package/show?package=libpng&project=Trunk libpng]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libprolog&project=Trunk libprolog]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libpthread-stubs&project=Trunk libpthread-stubs]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libqmlog&project=Trunk libqmlog]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=libqterminalmode&project=Trunk libqterminalmode]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libqtsparql&project=Trunk libqtsparql]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=libqtsparql-tracker-extensions&project=Trunk libqtsparql-tracker-extensions]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=libqttracker&project=Trunk libqttracker]
|rusty,lamadon,maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=libquill&project=Trunk libquill]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=libquillmetadata&project=Trunk libquillmetadata]
|maimishr
|
|-
|[http://build.meego.com/package/show?package=librapi2&project=Trunk librapi2]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=librds&project=Trunk librds]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libresource&project=Trunk libresource]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libresourceqt&project=Trunk libresourceqt]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=librsvg2&project=Trunk librsvg2]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsamplerate&project=Trunk libsamplerate]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsatsolver&project=Trunk libsatsolver]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=libseaside&project=Trunk libseaside]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=libsexy&project=Trunk libsexy]
|
|
|-
|[http://build.meego.com/package/show?package=libshare-ui&project=Trunk libshare-ui]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=libsigc++&project=Trunk libsigc++]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libsignon&project=Trunk libsignon]
|bwachter,pcapriotti
|devel:AccountsSSO
|-
|[http://build.meego.com/package/show?package=libsignon-glib&project=Trunk libsignon-glib]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libsignoncrypto-qt&project=Trunk libsignoncrypto-qt]
|mardy,pcapriotti
|
|-
|[http://build.meego.com/package/show?package=libsilc&project=Trunk libsilc]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libsmack&project=Trunk libsmack]
|rrware
|devel:security
|-
|[http://build.meego.com/package/show?package=libsmbios&project=Trunk libsmbios]
|
|
|-
|[http://build.meego.com/package/show?package=libsndfile&project=Trunk libsndfile]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libsocialweb&project=Trunk libsocialweb]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=libsocialweb-keys&project=Trunk libsocialweb-keys]
|
|
|-
|[http://build.meego.com/package/show?package=libsocialweb-qml&project=Trunk libsocialweb-qml]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libsocialweb-qt&project=Trunk libsocialweb-qt]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=libsoup&project=Trunk libsoup]
|
|
|-
|[http://build.meego.com/package/show?package=libspectre&project=Trunk libspectre]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libspiro&project=Trunk libspiro]
|
|
|-
|[http://build.meego.com/package/show?package=libstdc++-x86&project=Trunk libstdc++-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=libsynce&project=Trunk libsynce]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libsyncml&project=Trunk libsyncml]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=libtalloc&project=Trunk libtalloc]
|
|
|-
|[http://build.meego.com/package/show?package=libtar&project=Trunk libtar]
|
|
|-
|[http://build.meego.com/package/show?package=libtasn1&project=Trunk libtasn1]
|
|
|-
|[http://build.meego.com/package/show?package=libtdb&project=Trunk libtdb]
|
|
|-
|[http://build.meego.com/package/show?package=libtdb-compat&project=Trunk libtdb-compat]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=libtee&project=Trunk libtee]
|rrware
|
|-
|[http://build.meego.com/package/show?package=libtelepathy&project=Trunk libtelepathy]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=libthai&project=Trunk libthai]
|
|
|-
|[http://build.meego.com/package/show?package=libtheora&project=Trunk libtheora]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libthumbnailer&project=Trunk libthumbnailer]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=libtiff&project=Trunk libtiff]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libtool&project=Trunk libtool]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=libtrace&project=Trunk libtrace]
|
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=libuninameslist&project=Trunk libuninameslist]
|
|
|-
|[http://build.meego.com/package/show?package=libusb&project=Trunk libusb]
|
|
|-
|[http://build.meego.com/package/show?package=libusb1&project=Trunk libusb1]
|
|
|-
|[http://build.meego.com/package/show?package=libuser&project=Trunk libuser]
|
|
|-
|[http://build.meego.com/package/show?package=libutempter&project=Trunk libutempter]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libv4l&project=Trunk libv4l]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libva&project=Trunk libva]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libvisual&project=Trunk libvisual]
|
|
|-
|[http://build.meego.com/package/show?package=libvorbis&project=Trunk libvorbis]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=libwbxml2&project=Trunk libwbxml2]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=libwmf&project=Trunk libwmf]
|
|
|-
|[http://build.meego.com/package/show?package=libwnck&project=Trunk libwnck]
|
|
|-
|[http://build.meego.com/package/show?package=libwpd&project=Trunk libwpd]
|
|
|-
|[http://build.meego.com/package/show?package=libwpg&project=Trunk libwpg]
|
|
|-
|[http://build.meego.com/package/show?package=libwps&project=Trunk libwps]
|
|
|-
|[http://build.meego.com/package/show?package=libwsbm&project=Trunk libwsbm]
|
|
|-
|[http://build.meego.com/package/show?package=libxcb&project=Trunk libxcb]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libxkbfile&project=Trunk libxkbfile]
|pli1
|
|-
|[http://build.meego.com/package/show?package=libxklavier&project=Trunk libxklavier]
|xyl
|
|-
|[http://build.meego.com/package/show?package=libxml2&project=Trunk libxml2]
|nashif
|
|-
|[http://build.meego.com/package/show?package=libxml2-python&project=Trunk libxml2-python]
|nashif
|
|-
|[http://build.meego.com/package/show?package=libxslt&project=Trunk libxslt]
|jfding
|
|-
|[http://build.meego.com/package/show?package=libzip&project=Trunk libzip]
|yyang
|
|-
|[http://build.meego.com/package/show?package=libzypp&project=Trunk libzypp]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=libzypp-bindings&project=Trunk libzypp-bindings]
|yyang
|
|-
|[http://build.meego.com/package/show?package=link-grammar&project=Trunk link-grammar]
|
|
|-
|[http://build.meego.com/package/show?package=linux-firmware&project=Trunk linux-firmware]
|
|
|-
|[http://build.meego.com/package/show?package=lirc&project=Trunk lirc]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=lklug-fonts&project=Trunk lklug-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lockdev&project=Trunk lockdev]
|
|
|-
|[http://build.meego.com/package/show?package=logrotate&project=Trunk logrotate]
|
|
|-
|[http://build.meego.com/package/show?package=lohit-assamese-fonts&project=Trunk lohit-assamese-fonts]
|vivian
|
|-
|[http://build.meego.com/package/show?package=lohit-bengali-fonts&project=Trunk lohit-bengali-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-gujarati-fonts&project=Trunk lohit-gujarati-fonts]
|haoli
|
|-
|[http://build.meego.com/package/show?package=lohit-hindi-fonts&project=Trunk lohit-hindi-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-kannada-fonts&project=Trunk lohit-kannada-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-malayalam-fonts&project=Trunk lohit-malayalam-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-oriya-fonts&project=Trunk lohit-oriya-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-punjabi-fonts&project=Trunk lohit-punjabi-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-tamil-fonts&project=Trunk lohit-tamil-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=lohit-telugu-fonts&project=Trunk lohit-telugu-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=loudmouth&project=Trunk loudmouth]
|
|
|-
|[http://build.meego.com/package/show?package=lpsolve&project=Trunk lpsolve]
|
|
|-
|[http://build.meego.com/package/show?package=lrzsz&project=Trunk lrzsz]
|
|
|-
|[http://build.meego.com/package/show?package=lsof&project=Trunk lsof]
|
|
|-
|[http://build.meego.com/package/show?package=ltrace&project=Trunk ltrace]
|
|
|-
|[http://build.meego.com/package/show?package=lua&project=Trunk lua]
|jfding
|
|-
|[http://build.meego.com/package/show?package=lzo&project=Trunk lzo]
|yyang
|
|-
|[http://build.meego.com/package/show?package=m17n-contrib&project=Trunk m17n-contrib]
|
|
|-
|[http://build.meego.com/package/show?package=m17n-db&project=Trunk m17n-db]
|
|
|-
|[http://build.meego.com/package/show?package=m17n-lib&project=Trunk m17n-lib]
|
|
|-
|[http://build.meego.com/package/show?package=m2crypto&project=Trunk m2crypto]
|
|devel:security
|-
|[http://build.meego.com/package/show?package=m4&project=Trunk m4]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mad-developer&project=Trunk mad-developer]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=maemo-video-thumbnailer&project=Trunk maemo-video-thumbnailer]
|dlespiau,lamadon,maimishr
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=mailcap&project=Trunk mailcap]
|
|
|-
|[http://build.meego.com/package/show?package=mailx&project=Trunk mailx]
|
|
|-
|[http://build.meego.com/package/show?package=make&project=Trunk make]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=makebootfat&project=Trunk makebootfat]
|
|
|-
|[http://build.meego.com/package/show?package=man&project=Trunk man]
|
|
|-
|[http://build.meego.com/package/show?package=man-pages&project=Trunk man-pages]
|
|
|-
|[http://build.meego.com/package/show?package=marble&project=Trunk marble]
|
|
|-
|[http://build.meego.com/package/show?package=marmazon&project=Trunk marmazon]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=matchbox-keyboard&project=Trunk matchbox-keyboard]
|
|
|-
|[http://build.meego.com/package/show?package=matchbox-panel&project=Trunk matchbox-panel]
|
|
|-
|[http://build.meego.com/package/show?package=matchbox-window-manager&project=Trunk matchbox-window-manager]
|tebrandt,tracyg
|
|-
|[http://build.meego.com/package/show?package=mathml-fonts&project=Trunk mathml-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=mce&project=Trunk mce]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=mce-headers&project=Trunk mce-headers]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=meego-accelerator&project=Trunk meego-accelerator]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-bookmarks&project=Trunk meego-bookmarks]
|
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv5tel-sysroot&project=Trunk meego-cross-armv5tel-sysroot]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv7hl-sysroot&project=Trunk meego-cross-armv7hl-sysroot]
|austin
|
|-
|[http://build.meego.com/package/show?package=meego-cross-armv7l-sysroot&project=Trunk meego-cross-armv7l-sysroot]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=meego-cursor-theme&project=Trunk meego-cursor-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meego-handset-calendar&project=Trunk meego-handset-calendar]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-chat&project=Trunk meego-handset-chat]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-configs&project=Trunk meego-handset-configs]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer&project=Trunk meego-handset-dialer]
|sbryan,ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer-branding-meego&project=Trunk meego-handset-dialer-branding-meego]
|sbryan,ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-dialer-translations&project=Trunk meego-handset-dialer-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-email&project=Trunk meego-handset-email]
|ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-email-translations&project=Trunk meego-handset-email-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-icon-theme&project=Trunk meego-handset-icon-theme]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-mannequin&project=Trunk meego-handset-mannequin]
|sbryan,ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-music&project=Trunk meego-handset-music]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-music-branding-meego&project=Trunk meego-handset-music-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-people&project=Trunk meego-handset-people]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-photos&project=Trunk meego-handset-photos]
|krupert,ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-photos-branding-meego&project=Trunk meego-handset-photos-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-sms&project=Trunk meego-handset-sms]
|ceferron,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=meego-handset-sms-translations&project=Trunk meego-handset-sms-translations]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-socialweb&project=Trunk meego-handset-socialweb]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-sound-theme&project=Trunk meego-handset-sound-theme]
|ulf,tracyg
|
|-
|[http://build.meego.com/package/show?package=meego-handset-video&project=Trunk meego-handset-video]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-handset-video-branding-meego&project=Trunk meego-handset-video-branding-meego]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-ivi-configs&project=Trunk meego-ivi-configs]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=meego-lsb&project=Trunk meego-lsb]
|nashif
|
|-
|[http://build.meego.com/package/show?package=meego-menus&project=Trunk meego-menus]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-help&project=Trunk meego-netbook-help]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-intro&project=Trunk meego-netbook-intro]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-settings&project=Trunk meego-netbook-settings]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-theme&project=Trunk meego-netbook-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meego-netbook-user-skel&project=Trunk meego-netbook-user-skel]
|
|
|-
|[http://build.meego.com/package/show?package=meego-osc-plugins&project=Trunk meego-osc-plugins]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=meego-packaging-tools&project=Trunk meego-packaging-tools]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=meego-panel-applications&project=Trunk meego-panel-applications]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-datetime&project=Trunk meego-panel-datetime]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-devices&project=Trunk meego-panel-devices]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-myzone&project=Trunk meego-panel-myzone]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-networks&project=Trunk meego-panel-networks]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-pasteboard&project=Trunk meego-panel-pasteboard]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-people&project=Trunk meego-panel-people]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-status&project=Trunk meego-panel-status]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-web&project=Trunk meego-panel-web]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-panel-zones&project=Trunk meego-panel-zones]
|rbradford
|
|-
|[http://build.meego.com/package/show?package=meego-release&project=Trunk meego-release]
|nashif
|
|-
|[http://build.meego.com/package/show?package=meego-rpm-config&project=Trunk meego-rpm-config]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=meego-sdk-qemugl-addon&project=Trunk meego-sdk-qemugl-addon]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=meego-simulator-launcher&project=Trunk meego-simulator-launcher]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=meego-sound-theme&project=Trunk meego-sound-theme]
|
|
|-
|[http://build.meego.com/package/show?package=meegotouch-applauncherd&project=Trunk meegotouch-applauncherd]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-applifed&project=Trunk meegotouch-applifed]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-compositor&project=Trunk meegotouch-compositor]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-controlpanel&project=Trunk meegotouch-controlpanel]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-controlpanelapplets&project=Trunk meegotouch-controlpanelapplets]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-feedback&project=Trunk meegotouch-feedback]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-feedbackreactionmaps&project=Trunk meegotouch-feedbackreactionmaps]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-home&project=Trunk meegotouch-home]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodbridges&project=Trunk meegotouch-inputmethodbridges]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodengine&project=Trunk meegotouch-inputmethodengine]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodframework&project=Trunk meegotouch-inputmethodframework]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-inputmethodkeyboard&project=Trunk meegotouch-inputmethodkeyboard]
|krupert,araujo
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-qt-style&project=Trunk meegotouch-qt-style]
|boudra
|
|-
|[http://build.meego.com/package/show?package=meegotouch-systemtui&project=Trunk meegotouch-systemtui]
|
|
|-
|[http://build.meego.com/package/show?package=meegotouch-systemui&project=Trunk meegotouch-systemui]
|krupert,araujo
|
|-
|[http://build.meego.com/package/show?package=meegotouch-theme&project=Trunk meegotouch-theme]
|krupert,msafr
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouch-theme-meego&project=Trunk meegotouch-theme-meego]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-bluetooth&project=Trunk meegotouchcp-bluetooth]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-chat&project=Trunk meegotouchcp-chat]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-connman&project=Trunk meegotouchcp-connman]
|ceferron,ulf
|
|-
|[http://build.meego.com/package/show?package=meegotouchcp-datetime&project=Trunk meegotouchcp-datetime]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-language&project=Trunk meegotouchcp-language]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-regionformat&project=Trunk meegotouchcp-regionformat]
|krupert
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=meegotouchcp-socialweb&project=Trunk meegotouchcp-socialweb]
|ulf
|
|-
|[http://build.meego.com/package/show?package=meego-ux-translations&project=Trunk meego-ux-translations]
|pmccarty
|
|-
|[http://build.meego.com/package/show?package=meld&project=Trunk meld]
|
|
|-
|[http://build.meego.com/package/show?package=memuse&project=Trunk memuse]
|arjan
|
|-
|[http://build.meego.com/package/show?package=mesa&project=Trunk mesa]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=mesa-demos&project=Trunk mesa-demos]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=mic2&project=Trunk mic2]
|yyang
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=min&project=Trunk min]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=mingetty&project=Trunk mingetty]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=minicom&project=Trunk minicom]
|
|
|-
|[http://build.meego.com/package/show?package=mkcal&project=Trunk mkcal]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=mkdevnodes&project=Trunk mkdevnodes]
|
|
|-
|[http://build.meego.com/package/show?package=mkinitrd&project=Trunk mkinitrd]
|yyang
|
|-
|[http://build.meego.com/package/show?package=mlocate&project=Trunk mlocate]
|
|
|-
|[http://build.meego.com/package/show?package=mm-common&project=Trunk mm-common]
|
|
|-
|[http://build.meego.com/package/show?package=mobile-broadband-provider-info&project=Trunk mobile-broadband-provider-info]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-generic-backgrounds&project=Trunk moblin-generic-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-icon-theme&project=Trunk moblin-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=moblin-live&project=Trunk moblin-live]
|
|
|-
|[http://build.meego.com/package/show?package=module-init-tools&project=Trunk module-init-tools]
|
|
|-
|[http://build.meego.com/package/show?package=monit&project=Trunk monit]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=monitor-call-audio-setting-mid&project=Trunk monitor-call-audio-setting-mid]
|vivian
|
|-
|[http://build.meego.com/package/show?package=mono-addins&project=Trunk mono-addins]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=mono-core&project=Trunk mono-core]
|priya
|
|-
|[http://build.meego.com/package/show?package=mono-zeroconf&project=Trunk mono-zeroconf]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=mozilla-filesystem&project=Trunk mozilla-filesystem]
|jfding
|
|-
|[http://build.meego.com/package/show?package=mpage&project=Trunk mpage]
|
|
|-
|[http://build.meego.com/package/show?package=mpc&project=Trunk mpc]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mpc-x86&project=Trunk mpc-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=mpfr&project=Trunk mpfr]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=mpfr-x86&project=Trunk mpfr-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=mssf-certman&project=Trunk mssf-certman]
|rrware
|
|-
|[http://build.meego.com/package/show?package=mssf-crypto&project=Trunk mssf-crypto]
|rrware
|
|-
|[http://build.meego.com/package/show?package=mtd-utils&project=Trunk mtd-utils]
|
|
|-
|[http://build.meego.com/package/show?package=mtdev&project=Trunk mtdev]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=mtools&project=Trunk mtools]
|yyang
|
|-
|[http://build.meego.com/package/show?package=mutter&project=Trunk mutter]
|tomas
|devel:clutter
|-
|[http://build.meego.com/package/show?package=mutter-netbook&project=Trunk mutter-netbook]
|
|
|-
|[http://build.meego.com/package/show?package=mx&project=Trunk mx]
|
|
|-
|[http://build.meego.com/package/show?package=n900-camera-firmware&project=Trunk n900-camera-firmware]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nano&project=Trunk nano]
|
|
|-
|[http://build.meego.com/package/show?package=nasm&project=Trunk nasm]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=nautilus&project=Trunk nautilus]
|
|
|-
|[http://build.meego.com/package/show?package=nautilus-python&project=Trunk nautilus-python]
|
|
|-
|[http://build.meego.com/package/show?package=navit&project=Trunk navit]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=navit-maps&project=Trunk navit-maps]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=nc&project=Trunk nc]
|
|
|-
|[http://build.meego.com/package/show?package=ncurses&project=Trunk ncurses]
|jfding
|
|-
|[http://build.meego.com/package/show?package=ncurses-libs-x86&project=Trunk ncurses-libs-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=ndesk-dbus&project=Trunk ndesk-dbus]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=ndesk-dbus-glib&project=Trunk ndesk-dbus-glib]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=neon&project=Trunk neon]
|jfding
|
|-
|[http://build.meego.com/package/show?package=net-tools&project=Trunk net-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=netbook-backgrounds&project=Trunk netbook-backgrounds]
|
|
|-
|[http://build.meego.com/package/show?package=netbook-icon-theme&project=Trunk netbook-icon-theme]
|hbons
|
|-
|[http://build.meego.com/package/show?package=netpbm&project=Trunk netpbm]
|
|
|-
|[http://build.meego.com/package/show?package=neverball&project=Trunk neverball]
|
|
|-
|[http://build.meego.com/package/show?package=newt&project=Trunk newt]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=newt-python&project=Trunk newt-python]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=ngfd&project=Trunk ngfd]
|mantyharju
|
|-
|[http://build.meego.com/package/show?package=nodoka-theme-gnome&project=Trunk nodoka-theme-gnome]
|quanxianwang
|devel:gnome
|-
|[http://build.meego.com/package/show?package=nokia-n900-configs&project=Trunk nokia-n900-configs]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nokia-n900-rescue-initrd&project=Trunk nokia-n900-rescue-initrd]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=nokia-usb-networking&project=Trunk nokia-usb-networking]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=notification-daemon&project=Trunk notification-daemon]
|
|
|-
|[http://build.meego.com/package/show?package=notification-daemon-engine-nodoka&project=Trunk notification-daemon-engine-nodoka]
|
|
|-
|[http://build.meego.com/package/show?package=notify-python&project=Trunk notify-python]
|
|
|-
|[http://build.meego.com/package/show?package=notify-sharp&project=Trunk notify-sharp]
|mmeeks
|
|-
|[http://build.meego.com/package/show?package=nspr&project=Trunk nspr]
|jfding
|devel:base
|-
|[http://build.meego.com/package/show?package=nspr-x86&project=Trunk nspr-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=nss&project=Trunk nss]
|qzhao9
|devel:base
|-
|[http://build.meego.com/package/show?package=nss-mdns&project=Trunk nss-mdns]
|
|
|-
|[http://build.meego.com/package/show?package=nss-softokn-freebl-x86&project=Trunk nss-softokn-freebl-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=nss-x86&project=Trunk nss-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=ntp&project=Trunk ntp]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=o3read&project=Trunk o3read]
|
|
|-
|[http://build.meego.com/package/show?package=obex-data-server&project=Trunk obex-data-server]
|
|
|-
|[http://build.meego.com/package/show?package=obexd&project=Trunk obexd]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=ofono&project=Trunk ofono]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=ohm&project=Trunk ohm]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=ohm-plugins-misc&project=Trunk ohm-plugins-misc]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=opal&project=Trunk opal]
|
|
|-
|[http://build.meego.com/package/show?package=openconnect&project=Trunk openconnect]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=opengl-games-utils&project=Trunk opengl-games-utils]
|
|
|-
|[http://build.meego.com/package/show?package=openjade&project=Trunk openjade]
|
|
|-
|[http://build.meego.com/package/show?package=openjpeg&project=Trunk openjpeg]
|
|
|-
|[http://build.meego.com/package/show?package=openldap&project=Trunk openldap]
|
|
|-
|[http://build.meego.com/package/show?package=openobex&project=Trunk openobex]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=opensp&project=Trunk opensp]
|
|
|-
|[http://build.meego.com/package/show?package=openssh&project=Trunk openssh]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=openssl&project=Trunk openssl]
|qzhao9
|devel:security
|-
|[http://build.meego.com/package/show?package=openssl-certs&project=Trunk openssl-certs]
|
|
|-
|[http://build.meego.com/package/show?package=openvpn&project=Trunk openvpn]
|martin
|
|-
|[http://build.meego.com/package/show?package=orc&project=Trunk orc]
|lisayue
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=org-mode&project=Trunk org-mode]
|
|
|-
|[http://build.meego.com/package/show?package=osc&project=Trunk osc]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=ots&project=Trunk ots]
|
|
|-
|[http://build.meego.com/package/show?package=package-groups&project=Trunk package-groups]
|nashif
|
|-
|[http://build.meego.com/package/show?package=pacrunner&project=Trunk pacrunner]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=pakchois&project=Trunk pakchois]
|
|
|-
|[http://build.meego.com/package/show?package=pam&project=Trunk pam]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=pam_pkcs11&project=Trunk pam_pkcs11]
|
|
|-
|[http://build.meego.com/package/show?package=pango&project=Trunk pango]
|
|
|-
|[http://build.meego.com/package/show?package=pangomm&project=Trunk pangomm]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=paps&project=Trunk paps]
|
|
|-
|[http://build.meego.com/package/show?package=papyon&project=Trunk papyon]
|lixu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=parted&project=Trunk parted]
|vivian
|
|-
|[http://build.meego.com/package/show?package=passivetex&project=Trunk passivetex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=passwd&project=Trunk passwd]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=patch&project=Trunk patch]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=patch-x86&project=Trunk patch-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=patchelf&project=Trunk patchelf]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=patchutils&project=Trunk patchutils]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=pavucontrol&project=Trunk pavucontrol]
|vivian
|
|-
|[http://build.meego.com/package/show?package=pax&project=Trunk pax]
|
|
|-
|[http://build.meego.com/package/show?package=pciutils&project=Trunk pciutils]
|
|
|-
|[http://build.meego.com/package/show?package=pcre&project=Trunk pcre]
|
|
|-
|[http://build.meego.com/package/show?package=perl&project=Trunk perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Archive-Zip&project=Trunk perl-Archive-Zip]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Array-Compare&project=Trunk perl-Array-Compare]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Config-IniFiles&project=Trunk perl-Config-IniFiles]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Convert-ASN1&project=Trunk perl-Convert-ASN1]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Convert-BinHex&project=Trunk perl-Convert-BinHex]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Crypt-SSLeay&project=Trunk perl-Crypt-SSLeay]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Date-Manip&project=Trunk perl-Date-Manip]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Devel-StackTrace&project=Trunk perl-Devel-StackTrace]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Devel-Symdump&project=Trunk perl-Devel-Symdump]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Error&project=Trunk perl-Error]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-Depends&project=Trunk perl-ExtUtils-Depends]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-MakeMaker-Coverage&project=Trunk perl-ExtUtils-MakeMaker-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-ExtUtils-PkgConfig&project=Trunk perl-ExtUtils-PkgConfig]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-BaseDir&project=Trunk perl-File-BaseDir]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-DesktopEntry&project=Trunk perl-File-DesktopEntry]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-MimeInfo&project=Trunk perl-File-MimeInfo]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-File-Which&project=Trunk perl-File-Which]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Finance-Quote&project=Trunk perl-Finance-Quote]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Font-TTF&project=Trunk perl-Font-TTF]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Glib&project=Trunk perl-Glib]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Parser&project=Trunk perl-HTML-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-TableExtract&project=Trunk perl-HTML-TableExtract]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Tagset&project=Trunk perl-HTML-Tagset]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-HTML-Tree&project=Trunk perl-HTML-Tree]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-Socket-INET6&project=Trunk perl-IO-Socket-INET6]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-Socket-SSL&project=Trunk perl-IO-Socket-SSL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-IO-stringy&project=Trunk perl-IO-stringy]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-JSON&project=Trunk perl-JSON]
|qzhao9,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=perl-MIME-Lite&project=Trunk perl-MIME-Lite]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-MIME-tools&project=Trunk perl-MIME-tools]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-MailTools&project=Trunk perl-MailTools]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-LibIDN&project=Trunk perl-Net-LibIDN]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-SMTP-SSL&project=Trunk perl-Net-SMTP-SSL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Net-SSLeay&project=Trunk perl-Net-SSLeay]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Parse-Yapp&project=Trunk perl-Parse-Yapp]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Pod-Coverage&project=Trunk perl-Pod-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SDL&project=Trunk perl-SDL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SGMLSpm&project=Trunk perl-SGMLSpm]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SOAP-Lite&project=Trunk perl-SOAP-Lite]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SVG&project=Trunk perl-SVG]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-SVG-Parser&project=Trunk perl-SVG-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Socket6&project=Trunk perl-Socket6]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Sub-Uplevel&project=Trunk perl-Sub-Uplevel]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Exception&project=Trunk perl-Test-Exception]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-MockObject&project=Trunk perl-Test-MockObject]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-NoWarnings&project=Trunk perl-Test-NoWarnings]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Number-Delta&project=Trunk perl-Test-Number-Delta]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Pod&project=Trunk perl-Test-Pod]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Pod-Coverage&project=Trunk perl-Test-Pod-Coverage]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Tester&project=Trunk perl-Test-Tester]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Test-Warn&project=Trunk perl-Test-Warn]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Text-Unidecode&project=Trunk perl-Text-Unidecode]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tie-IxHash&project=Trunk perl-Tie-IxHash]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-TimeDate&project=Trunk perl-TimeDate]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tk&project=Trunk perl-Tk]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-Tree-DAG_Node&project=Trunk perl-Tree-DAG_Node]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-UNIVERSAL-can&project=Trunk perl-UNIVERSAL-can]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-UNIVERSAL-isa&project=Trunk perl-UNIVERSAL-isa]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-URI&project=Trunk perl-URI]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-DOM&project=Trunk perl-XML-DOM]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-LibXML&project=Trunk perl-XML-LibXML]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-NamespaceSupport&project=Trunk perl-XML-NamespaceSupport]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-Parser&project=Trunk perl-XML-Parser]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-RegExp&project=Trunk perl-XML-RegExp]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-SAX&project=Trunk perl-XML-SAX]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-Simple&project=Trunk perl-XML-Simple]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-TreeBuilder&project=Trunk perl-XML-TreeBuilder]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-XML-XQL&project=Trunk perl-XML-XQL]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-YAML&project=Trunk perl-YAML]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-gettext&project=Trunk perl-gettext]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-libwww-perl&project=Trunk perl-libwww-perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=perl-libxml-perl&project=Trunk perl-libxml-perl]
|quanxianwang
|devel:languages:perl
|-
|[http://build.meego.com/package/show?package=persistman&project=Trunk persistman]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=phidgetlinux&project=Trunk phidgetlinux]
|xing
|
|-
|[http://build.meego.com/package/show?package=phonesim&project=Trunk phonesim]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=phonon&project=Trunk phonon]
|xiaoqiang,quanxianwang,boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=pidgin&project=Trunk pidgin]
|
|
|-
|[http://build.meego.com/package/show?package=pidgin-sipe&project=Trunk pidgin-sipe]
|
|
|-
|[http://build.meego.com/package/show?package=pixman&project=Trunk pixman]
|xyl
|
|-
|[http://build.meego.com/package/show?package=pkcs11-helper&project=Trunk pkcs11-helper]
|martin
|
|-
|[http://build.meego.com/package/show?package=pkgconfig&project=Trunk pkgconfig]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=plib&project=Trunk plib]
|
|
|-
|[http://build.meego.com/package/show?package=plymouth-lite&project=Trunk plymouth-lite]
|
|
|-
|[http://build.meego.com/package/show?package=pm-utils&project=Trunk pm-utils]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=pmtools&project=Trunk pmtools]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=pocketsphinx&project=Trunk pocketsphinx]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=poedit&project=Trunk poedit]
|
|
|-
|[http://build.meego.com/package/show?package=policy-settings-basic-mfld&project=Trunk policy-settings-basic-mfld]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=policy-settings-basic-n900&project=Trunk policy-settings-basic-n900]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=policy-settings-tablet&project=Trunk policy-settings-tablet]
|
|
|-
|[http://build.meego.com/package/show?package=polkit&project=Trunk polkit]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=polkit-gnome&project=Trunk polkit-gnome]
|yyin2
|devel:gnome
|-
|[http://build.meego.com/package/show?package=poppler&project=Trunk poppler]
|xiaoqiang,quanxianwang,boudra
|
|-
|[http://build.meego.com/package/show?package=poppler-data&project=Trunk poppler-data]
|boudra
|
|-
|[http://build.meego.com/package/show?package=poppler-qt&project=Trunk poppler-qt]
|boudra
|
|-
|[http://build.meego.com/package/show?package=popt&project=Trunk popt]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=popt-x86&project=Trunk popt-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=post-build-checks&project=Trunk post-build-checks]
|nashif
|
|-
|[http://build.meego.com/package/show?package=poster&project=Trunk poster]
|
|
|-
|[http://build.meego.com/package/show?package=powerstatemgr&project=Trunk powerstatemgr]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=powertop&project=Trunk powertop]
|arjan
|
|-
|[http://build.meego.com/package/show?package=ppl&project=Trunk ppl]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=ppp&project=Trunk ppp]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=prelink&project=Trunk prelink]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=procps&project=Trunk procps]
|
|
|-
|[http://build.meego.com/package/show?package=psb-headers&project=Trunk psb-headers]
|
|
|-
|[http://build.meego.com/package/show?package=psmisc&project=Trunk psmisc]
|yyang
|
|-
|[http://build.meego.com/package/show?package=psutils&project=Trunk psutils]
|
|
|-
|[http://build.meego.com/package/show?package=pth&project=Trunk pth]
|
|
|-
|[http://build.meego.com/package/show?package=ptlib&project=Trunk ptlib]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pulseaudio&project=Trunk pulseaudio]
|vivian
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-meego&project=Trunk pulseaudio-modules-meego]
|
|devel:multimedia
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-mfld&project=Trunk pulseaudio-modules-mfld]
|ulf
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-modules-n900&project=Trunk pulseaudio-modules-n900]
|
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-policy-enforcement&project=Trunk pulseaudio-policy-enforcement]
|mlehtonen
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-settings-mfld&project=Trunk pulseaudio-settings-mfld]
|
|
|-
|[http://build.meego.com/package/show?package=pulseaudio-settings-n900&project=Trunk pulseaudio-settings-n900]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=pyOpenSSL&project=Trunk pyOpenSSL]
|
|
|-
|[http://build.meego.com/package/show?package=pycairo&project=Trunk pycairo]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pyclutter&project=Trunk pyclutter]
|rbradford,ebassi
|devel:clutter
|-
|[http://build.meego.com/package/show?package=pyclutter-gtk&project=Trunk pyclutter-gtk]
|rbradford,ebassi
|devel:clutter
|-
|[http://build.meego.com/package/show?package=pygobject2&project=Trunk pygobject2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygpgme&project=Trunk pygpgme]
|
|
|-
|[http://build.meego.com/package/show?package=pygtk2&project=Trunk pygtk2]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygtkglext&project=Trunk pygtkglext]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=pygtksourceview&project=Trunk pygtksourceview]
|
|
|-
|[http://build.meego.com/package/show?package=pykickstart&project=Trunk pykickstart]
|vivian
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=pyorbit&project=Trunk pyorbit]
|
|
|-
|[http://build.meego.com/package/show?package=pyparted&project=Trunk pyparted]
|vivian
|
|-
|[http://build.meego.com/package/show?package=python&project=Trunk python]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-Coherence&project=Trunk python-Coherence]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-ZSI&project=Trunk python-ZSI]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-adns&project=Trunk python-adns]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-chardet&project=Trunk python-chardet]
|jiachenghu
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-cheetah&project=Trunk python-cheetah]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-configobj&project=Trunk python-configobj]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-crypto&project=Trunk python-crypto]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-dateutil&project=Trunk python-dateutil]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-decorator&project=Trunk python-decorator]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-docutils&project=Trunk python-docutils]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-dtopt&project=Trunk python-dtopt]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-enchant&project=Trunk python-enchant]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-formencode&project=Trunk python-formencode]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-fpconst&project=Trunk python-fpconst]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-gdata&project=Trunk python-gdata]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-imaging&project=Trunk python-imaging]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-iniparse&project=Trunk python-iniparse]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-louie&project=Trunk python-louie]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-lxml&project=Trunk python-lxml]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-magic&project=Trunk python-magic]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-markdown&project=Trunk python-markdown]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-mutagen&project=Trunk python-mutagen]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-nose&project=Trunk python-nose]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-numeric&project=Trunk python-numeric]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-paste&project=Trunk python-paste]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-paste-deploy&project=Trunk python-paste-deploy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-pycurl&project=Trunk python-pycurl]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-pygments&project=Trunk python-pygments]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-reportlab&project=Trunk python-reportlab]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-setuptools&project=Trunk python-setuptools]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-sexy&project=Trunk python-sexy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-simplejson&project=Trunk python-simplejson]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-sqlite2&project=Trunk python-sqlite2]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-telepathy&project=Trunk python-telepathy]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-tempita&project=Trunk python-tempita]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-toscawidgets&project=Trunk python-toscawidgets]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-tw-forms&project=Trunk python-tw-forms]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted&project=Trunk python-twisted]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-conch&project=Trunk python-twisted-conch]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-core&project=Trunk python-twisted-core]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-lore&project=Trunk python-twisted-lore]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-mail&project=Trunk python-twisted-mail]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-names&project=Trunk python-twisted-names]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-news&project=Trunk python-twisted-news]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-runner&project=Trunk python-twisted-runner]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-web&project=Trunk python-twisted-web]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-web2&project=Trunk python-twisted-web2]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-twisted-words&project=Trunk python-twisted-words]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-urlgrabber&project=Trunk python-urlgrabber]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-webob&project=Trunk python-webob]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-which&project=Trunk python-which]
|
|
|-
|[http://build.meego.com/package/show?package=python-wsgiproxy&project=Trunk python-wsgiproxy]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=python-xklavier&project=Trunk python-xklavier]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-zope-filesystem&project=Trunk python-zope-filesystem]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=python-zope-interface&project=Trunk python-zope-interface]
|quanxianwang
|devel:languages:python
|-
|[http://build.meego.com/package/show?package=pytz&project=Trunk pytz]
|
|
|-
|[http://build.meego.com/package/show?package=pyxdg&project=Trunk pyxdg]
|jiachenghu
|
|-
|[http://build.meego.com/package/show?package=qca2&project=Trunk qca2]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qca2-ossl&project=Trunk qca2-ossl]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qjson&project=Trunk qjson]
|rusty
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qmf&project=Trunk qmf]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qmsystem&project=Trunk qmsystem]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=qpid-cpp&project=Trunk qpid-cpp]
|jokylanp
|
|-
|[http://build.meego.com/package/show?package=qt&project=Trunk qt]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-creator&project=Trunk qt-creator]
|priya,boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-mobility&project=Trunk qt-mobility]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qt-mobility-geoservices-cloudmade&project=Trunk qt-mobility-geoservices-cloudmade]
|mikeleib
|
|-
|[http://build.meego.com/package/show?package=qt-mobility-mediaservice-dbus&project=Trunk qt-mobility-mediaservice-dbus]
|
|
|-
|[http://build.meego.com/package/show?package=qt-obex-ftp-library&project=Trunk qt-obex-ftp-library]
|
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=qtcontacts-tracker&project=Trunk qtcontacts-tracker]
|
|devel:people
|-
|[http://build.meego.com/package/show?package=qterminalmodeclient&project=Trunk qterminalmodeclient]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=qtgstreamer&project=Trunk qtgstreamer]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=qttas-server&project=Trunk qttas-server]
|talahtel
|
|-
|[http://build.meego.com/package/show?package=qtwebkit&project=Trunk qtwebkit]
|boudra
|devel:qt-mtf
|-
|[http://build.meego.com/package/show?package=quicksynergy&project=Trunk quicksynergy]
|
|
|-
|[http://build.meego.com/package/show?package=quillimagefilter&project=Trunk quillimagefilter]
|
|
|-
|[http://build.meego.com/package/show?package=quilt&project=Trunk quilt]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rar-kernel-headers&project=Trunk rar-kernel-headers]
|ulf
|
|-
|[http://build.meego.com/package/show?package=rarian&project=Trunk rarian]
|
|
|-
|[http://build.meego.com/package/show?package=rdsd&project=Trunk rdsd]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=rdsquery&project=Trunk rdsquery]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=readline&project=Trunk readline]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=recode&project=Trunk recode]
|
|
|-
|[http://build.meego.com/package/show?package=rest&project=Trunk rest]
|ross
|
|-
|[http://build.meego.com/package/show?package=rfkill&project=Trunk rfkill]
|erwanmahe
|
|-
|[http://build.meego.com/package/show?package=rhpl&project=Trunk rhpl]
|vivian
|
|-
|[http://build.meego.com/package/show?package=rhythmbox&project=Trunk rhythmbox]
|
|
|-
|[http://build.meego.com/package/show?package=rootfiles&project=Trunk rootfiles]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpm&project=Trunk rpm]
|nashif,xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=rpm-build-x86&project=Trunk rpm-build-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpm-libs-x86&project=Trunk rpm-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpm-python&project=Trunk rpm-python]
|nashif
|
|-
|[http://build.meego.com/package/show?package=rpm-x86&project=Trunk rpm-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpmcheck&project=Trunk rpmcheck]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmdevtools&project=Trunk rpmdevtools]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmlint&project=Trunk rpmlint]
|nashif
|devel:building
|-
|[http://build.meego.com/package/show?package=rpmlint-Moblin&project=Trunk rpmlint-Moblin]
|nashif
|devel:building
|-
|[http://build.meego.com/package/show?package=rpmlint-mini&project=Trunk rpmlint-mini]
|nashif
|devel:building
|-
|[http://build.meego.com/package/show?package=rpmlint-mini-x86&project=Trunk rpmlint-mini-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=rpmorphan&project=Trunk rpmorphan]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rpmreaper&project=Trunk rpmreaper]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=rsync&project=Trunk rsync]
|
|
|-
|[http://build.meego.com/package/show?package=rtkit&project=Trunk rtkit]
|yyang
|
|-
|[http://build.meego.com/package/show?package=ruby&project=Trunk ruby]
|jfding
|
|-
|[http://build.meego.com/package/show?package=rygel&project=Trunk rygel]
|tosantak
|
|-
|[http://build.meego.com/package/show?package=samba&project=Trunk samba]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=sample-media&project=Trunk sample-media]
|auke
|
|-
|[http://build.meego.com/package/show?package=sane-backends&project=Trunk sane-backends]
|
|
|-
|[http://build.meego.com/package/show?package=scim&project=Trunk scim]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-anthy&project=Trunk scim-anthy]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-bridge&project=Trunk scim-bridge]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-chewing&project=Trunk scim-chewing]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-hangul&project=Trunk scim-hangul]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-m17n&project=Trunk scim-m17n]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-panel-vkb-gtk&project=Trunk scim-panel-vkb-gtk]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-pinyin&project=Trunk scim-pinyin]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scim-skk&project=Trunk scim-skk]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=scons&project=Trunk scons]
|
|
|-
|[http://build.meego.com/package/show?package=screen&project=Trunk screen]
|nashif
|
|-
|[http://build.meego.com/package/show?package=sed&project=Trunk sed]
|yanli
|
|-
|[http://build.meego.com/package/show?package=sed-x86&project=Trunk sed-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=sensorfw&project=Trunk sensorfw]
|mlehtonen
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=sensorfw-pegatron&project=Trunk sensorfw-pegatron]
|
|
|-
|[http://build.meego.com/package/show?package=setup&project=Trunk setup]
|
|
|-
|[http://build.meego.com/package/show?package=setuptool&project=Trunk setuptool]
|
|
|-
|[http://build.meego.com/package/show?package=sg3_utils&project=Trunk sg3_utils]
|
|
|-
|[http://build.meego.com/package/show?package=sgml-common&project=Trunk sgml-common]
|
|
|-
|[http://build.meego.com/package/show?package=shadow-utils&project=Trunk shadow-utils]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=shared-mime-info&project=Trunk shared-mime-info]
|vivian
|
|-
|[http://build.meego.com/package/show?package=sharutils&project=Trunk sharutils]
|yyang
|
|-
|[http://build.meego.com/package/show?package=signon-digest&project=Trunk signon-digest]
|pcapriotti
|
|-
|[http://build.meego.com/package/show?package=signon-oauth2&project=Trunk signon-oauth2]
|senko,pcapriotti
|
|-
|[http://build.meego.com/package/show?package=simple-scan&project=Trunk simple-scan]
|
|
|-
|[http://build.meego.com/package/show?package=skkdic&project=Trunk skkdic]
|
|
|-
|[http://build.meego.com/package/show?package=slang&project=Trunk slang]
|
|
|-
|[http://build.meego.com/package/show?package=slib&project=Trunk slib]
|
|
|-
|[http://build.meego.com/package/show?package=smartmontools&project=Trunk smartmontools]
|
|
|-
|[http://build.meego.com/package/show?package=smem&project=Trunk smem]
|auke
|
|-
|[http://build.meego.com/package/show?package=smshistory&project=Trunk smshistory]
|krupert,ulf
|devel:ux:handset
|-
|[http://build.meego.com/package/show?package=sofia-sip&project=Trunk sofia-sip]
|
|
|-
|[http://build.meego.com/package/show?package=sound-theme-freedesktop&project=Trunk sound-theme-freedesktop]
|
|
|-
|[http://build.meego.com/package/show?package=soundtouch&project=Trunk soundtouch]
|
|
|-
|[http://build.meego.com/package/show?package=spectacle&project=Trunk spectacle]
|jfding
|devel:tools:building
|-
|[http://build.meego.com/package/show?package=speech-dispatcher&project=Trunk speech-dispatcher]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=speex&project=Trunk speex]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=sphinxbase&project=Trunk sphinxbase]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=sqlite&project=Trunk sqlite]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sqlite-x86&project=Trunk sqlite-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=squashfs-tools&project=Trunk squashfs-tools]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sreadahead&project=Trunk sreadahead]
|auke
|
|-
|[http://build.meego.com/package/show?package=ssmtp&project=Trunk ssmtp]
|
|
|-
|[http://build.meego.com/package/show?package=startup-notification&project=Trunk startup-notification]
|jfding
|
|-
|[http://build.meego.com/package/show?package=strace&project=Trunk strace]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=subversion&project=Trunk subversion]
|
|
|-
|[http://build.meego.com/package/show?package=sudo&project=Trunk sudo]
|yanli
|devel:base
|-
|[http://build.meego.com/package/show?package=swi-prolog&project=Trunk swi-prolog]
|mlehtonen
|devel:resourcepolicy
|-
|[http://build.meego.com/package/show?package=swig&project=Trunk swig]
|
|devel:base
|-
|[http://build.meego.com/package/show?package=syncevolution&project=Trunk syncevolution]
|pohly
|
|-
|[http://build.meego.com/package/show?package=syncevolution-gtk&project=Trunk syncevolution-gtk]
|pohly
|
|-
|[http://build.meego.com/package/show?package=synergy&project=Trunk synergy]
|
|
|-
|[http://build.meego.com/package/show?package=sysfsutils&project=Trunk sysfsutils]
|
|
|-
|[http://build.meego.com/package/show?package=sysklogd&project=Trunk sysklogd]
|
|
|-
|[http://build.meego.com/package/show?package=syslinux&project=Trunk syslinux]
|yyang
|
|-
|[http://build.meego.com/package/show?package=sysprof&project=Trunk sysprof]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-boot&project=Trunk system-config-boot]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=system-config-date&project=Trunk system-config-date]
|vivian
|
|-
|[http://build.meego.com/package/show?package=system-config-date-docs&project=Trunk system-config-date-docs]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=system-config-language&project=Trunk system-config-language]
|
|
|-
|[http://build.meego.com/package/show?package=system-config-printer&project=Trunk system-config-printer]
|itachi
|
|-
|[http://build.meego.com/package/show?package=system-config-users&project=Trunk system-config-users]
|
|
|-
|[http://build.meego.com/package/show?package=sysvinit&project=Trunk sysvinit]
|
|
|-
|[http://build.meego.com/package/show?package=t1lib&project=Trunk t1lib]
|
|
|-
|[http://build.meego.com/package/show?package=taglib&project=Trunk taglib]
|
|
|-
|[http://build.meego.com/package/show?package=taglib-sharp&project=Trunk taglib-sharp]
|abock
|
|-
|[http://build.meego.com/package/show?package=tar&project=Trunk tar]
|yanli
|
|-
|[http://build.meego.com/package/show?package=tar-x86&project=Trunk tar-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=tasks&project=Trunk tasks]
|
|
|-
|[http://build.meego.com/package/show?package=tcl&project=Trunk tcl]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tcp_wrappers&project=Trunk tcp_wrappers]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tcpdump&project=Trunk tcpdump]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tcsh&project=Trunk tcsh]
|
|
|-
|[http://build.meego.com/package/show?package=teckit&project=Trunk teckit]
|
|
|-
|[http://build.meego.com/package/show?package=telepathy-butterfly&project=Trunk telepathy-butterfly]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-farsight&project=Trunk telepathy-farsight]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-filesystem&project=Trunk telepathy-filesystem]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-gabble&project=Trunk telepathy-gabble]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-glib&project=Trunk telepathy-glib]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-haze&project=Trunk telepathy-haze]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-idle&project=Trunk telepathy-idle]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-logger&project=Trunk telepathy-logger]
|zabaluev,rbradford
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-mission-control&project=Trunk telepathy-mission-control]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-qt4&project=Trunk telepathy-qt4]
|zabaluev
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-ring&project=Trunk telepathy-ring]
|bwachter
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-salut&project=Trunk telepathy-salut]
|huaxu
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-sofiasip&project=Trunk telepathy-sofiasip]
|bwachter,zabaluev,pcapriotti
|devel:telepathy
|-
|[http://build.meego.com/package/show?package=telepathy-stream-engine&project=Trunk telepathy-stream-engine]
|senko
|
|-
|[http://build.meego.com/package/show?package=test-definition&project=Trunk test-definition]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=testrunner-lite&project=Trunk testrunner-lite]
|timoph,jokylanp
|
|-
|[http://build.meego.com/package/show?package=texi2html&project=Trunk texi2html]
|
|
|-
|[http://build.meego.com/package/show?package=texinfo&project=Trunk texinfo]
|
|
|-
|[http://build.meego.com/package/show?package=texlive&project=Trunk texlive]
|yanli
|
|-
|[http://build.meego.com/package/show?package=texlive-texmf&project=Trunk texlive-texmf]
|yanli
|
|-
|[http://build.meego.com/package/show?package=texlive-texmf-errata&project=Trunk texlive-texmf-errata]
|yanli
|
|-
|[http://build.meego.com/package/show?package=ti-kfmapp&project=Trunk ti-kfmapp]
|danisr
|
|-
|[http://build.meego.com/package/show?package=ti-uim&project=Trunk ti-uim]
|erwanmahe
|
|-
|[http://build.meego.com/package/show?package=tig&project=Trunk tig]
|
|
|-
|[http://build.meego.com/package/show?package=time&project=Trunk time]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=timed&project=Trunk timed]
|tapioran
|devel:systemsw
|-
|[http://build.meego.com/package/show?package=tinycdb&project=Trunk tinycdb]
|rusty
|
|-
|[http://build.meego.com/package/show?package=tix&project=Trunk tix]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tk&project=Trunk tk]
|jfding
|
|-
|[http://build.meego.com/package/show?package=tmpwatch&project=Trunk tmpwatch]
|
|
|-
|[http://build.meego.com/package/show?package=tone-generator&project=Trunk tone-generator]
|
|
|-
|[http://build.meego.com/package/show?package=totem&project=Trunk totem]
|
|
|-
|[http://build.meego.com/package/show?package=totem-pl-parser&project=Trunk totem-pl-parser]
|
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=tpm-tools&project=Trunk tpm-tools]
|
|
|-
|[http://build.meego.com/package/show?package=traceroute&project=Trunk traceroute]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=tracker&project=Trunk tracker]
|lamadon
|devel:contentfw
|-
|[http://build.meego.com/package/show?package=tracker-upnp&project=Trunk tracker-upnp]
|jku
|devel:tv
|-
|[http://build.meego.com/package/show?package=transfer-ui&project=Trunk transfer-ui]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=transifex-client&project=Trunk transifex-client]
|auke
|
|-
|[http://build.meego.com/package/show?package=transmission&project=Trunk transmission]
|
|
|-
|[http://build.meego.com/package/show?package=trousers&project=Trunk trousers]
|
|
|-
|[http://build.meego.com/package/show?package=tsc2007-config&project=Trunk tsc2007-config]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=ttmkfdir&project=Trunk ttmkfdir]
|
|
|-
|[http://build.meego.com/package/show?package=tumbler&project=Trunk tumbler]
|lamadon,maimishr
|
|-
|[http://build.meego.com/package/show?package=twitter-glib&project=Trunk twitter-glib]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=tzdata&project=Trunk tzdata]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=u-boot&project=Trunk u-boot]
|nm
|
|-
|[http://build.meego.com/package/show?package=udev&project=Trunk udev]
|kai,zhongxin
|devel:udev
|-
|[http://build.meego.com/package/show?package=udev-rules-handset-mid&project=Trunk udev-rules-handset-mid]
|
|
|-
|[http://build.meego.com/package/show?package=udev-rules-netbook&project=Trunk udev-rules-netbook]
|
|
|-
|[http://build.meego.com/package/show?package=udev-rules-nokia-n900&project=Trunk udev-rules-nokia-n900]
|cvm
|devel:devices:n900
|-
|[http://build.meego.com/package/show?package=udiskie&project=Trunk udiskie]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=udisks&project=Trunk udisks]
|vivian,yyin2,zhongxin
|
|-
|[http://build.meego.com/package/show?package=udisks-helper-extras&project=Trunk udisks-helper-extras]
|zhongxin
|
|-
|[http://build.meego.com/package/show?package=un-core-fonts&project=Trunk un-core-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=unique&project=Trunk unique]
|
|
|-
|[http://build.meego.com/package/show?package=unzip&project=Trunk unzip]
|yyang
|
|-
|[http://build.meego.com/package/show?package=upower&project=Trunk upower]
|yyin2,zhongxin
|
|-
|[http://build.meego.com/package/show?package=urw-fonts&project=Trunk urw-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=usb-modeswitch&project=Trunk usb-modeswitch]
|
|
|-
|[http://build.meego.com/package/show?package=usb-modeswitch-data&project=Trunk usb-modeswitch-data]
|
|
|-
|[http://build.meego.com/package/show?package=usbutils&project=Trunk usbutils]
|
|
|-
|[http://build.meego.com/package/show?package=usermode&project=Trunk usermode]
|
|
|-
|[http://build.meego.com/package/show?package=usleep&project=Trunk usleep]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=utfs&project=Trunk utfs]
|boudra
|devel:tools:sdk:target
|-
|[http://build.meego.com/package/show?package=uthash&project=Trunk uthash]
|rrware
|
|-
|[http://build.meego.com/package/show?package=util-linux-ng&project=Trunk util-linux-ng]
|yanli
|
|-
|[http://build.meego.com/package/show?package=uuid&project=Trunk uuid]
|
|
|-
|[http://build.meego.com/package/show?package=uxlaunch&project=Trunk uxlaunch]
|auke
|
|-
|[http://build.meego.com/package/show?package=v8&project=Trunk v8]
|
|devel:browser
|-
|[http://build.meego.com/package/show?package=vala&project=Trunk vala]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=valgrind&project=Trunk valgrind]
|qzhao9
|
|-
|[http://build.meego.com/package/show?package=vamp-plugin-sdk&project=Trunk vamp-plugin-sdk]
|
|
|-
|[http://build.meego.com/package/show?package=vibrant-icon-theme&project=Trunk vibrant-icon-theme]
|
|
|-
|[http://build.meego.com/package/show?package=vim&project=Trunk vim]
|
|
|-
|[http://build.meego.com/package/show?package=vlgothic-fonts&project=Trunk vlgothic-fonts]
|yanli
|
|-
|[http://build.meego.com/package/show?package=voicecallhistory&project=Trunk voicecallhistory]
|krupert,ulf
|
|-
|[http://build.meego.com/package/show?package=vorbis-tools&project=Trunk vorbis-tools]
|
|
|-
|[http://build.meego.com/package/show?package=vpnc&project=Trunk vpnc]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=vte&project=Trunk vte]
|xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=w3m&project=Trunk w3m]
|
|
|-
|[http://build.meego.com/package/show?package=webupload-engine&project=Trunk webupload-engine]
|teemu.hukkanen
|
|-
|[http://build.meego.com/package/show?package=wget&project=Trunk wget]
|jfding
|
|-
|[http://build.meego.com/package/show?package=wildmidi&project=Trunk wildmidi]
|lisayue
|
|-
|[http://build.meego.com/package/show?package=wimax-tools&project=Trunk wimax-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wireless-regdb&project=Trunk wireless-regdb]
|cleech
|
|-
|[http://build.meego.com/package/show?package=wireless-tools&project=Trunk wireless-tools]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wlanconfig&project=Trunk wlanconfig]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wpa_supplicant&project=Trunk wpa_supplicant]
|martin
|devel:connectivity
|-
|[http://build.meego.com/package/show?package=wv&project=Trunk wv]
|
|
|-
|[http://build.meego.com/package/show?package=wxGTK&project=Trunk wxGTK]
|
|
|-
|[http://build.meego.com/package/show?package=wxPython&project=Trunk wxPython]
|quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xbacklight&project=Trunk xbacklight]
|
|
|-
|[http://build.meego.com/package/show?package=xbindkeys&project=Trunk xbindkeys]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xcb-proto&project=Trunk xcb-proto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xcb-util&project=Trunk xcb-util]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xdg-user-dirs&project=Trunk xdg-user-dirs]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xdg-user-dirs-gtk&project=Trunk xdg-user-dirs-gtk]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=xdg-utils&project=Trunk xdg-utils]
|xiaoqiang,quanxianwang,boudra
|
|-
|[http://build.meego.com/package/show?package=xdvipdfmx&project=Trunk xdvipdfmx]
|
|
|-
|[http://build.meego.com/package/show?package=xerces-c&project=Trunk xerces-c]
|
|
|-
|[http://build.meego.com/package/show?package=xhtml1-dtds&project=Trunk xhtml1-dtds]
|
|
|-
|[http://build.meego.com/package/show?package=xhtml2fo-style-xsl&project=Trunk xhtml2fo-style-xsl]
|
|
|-
|[http://build.meego.com/package/show?package=xinetd&project=Trunk xinetd]
|
|
|-
|[http://build.meego.com/package/show?package=xinput_calibrator&project=Trunk xinput_calibrator]
|
|
|-
|[http://build.meego.com/package/show?package=xkeyboard-config&project=Trunk xkeyboard-config]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xmlrpc-c&project=Trunk xmlrpc-c]
|
|
|-
|[http://build.meego.com/package/show?package=xmltex&project=Trunk xmltex]
|bwachter
|
|-
|[http://build.meego.com/package/show?package=xmlto&project=Trunk xmlto]
|jfding
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-apps&project=Trunk xorg-x11-apps]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-evdev&project=Trunk xorg-x11-drv-evdev]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-evtouch&project=Trunk xorg-x11-drv-evtouch]
|tracyg
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-fbdev&project=Trunk xorg-x11-drv-fbdev]
|kad
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-intel&project=Trunk xorg-x11-drv-intel]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-joystick&project=Trunk xorg-x11-drv-joystick]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-keyboard&project=Trunk xorg-x11-drv-keyboard]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-kvm&project=Trunk xorg-x11-drv-kvm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mga&project=Trunk xorg-x11-drv-mga]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mouse&project=Trunk xorg-x11-drv-mouse]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-mtev&project=Trunk xorg-x11-drv-mtev]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-omapfb&project=Trunk xorg-x11-drv-omapfb]
|boudra
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-synaptics&project=Trunk xorg-x11-drv-synaptics]
|yanli
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vesa&project=Trunk xorg-x11-drv-vesa]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vmmouse&project=Trunk xorg-x11-drv-vmmouse]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-vmware&project=Trunk xorg-x11-drv-vmware]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-void&project=Trunk xorg-x11-drv-void]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-drv-wacom&project=Trunk xorg-x11-drv-wacom]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-filesystem&project=Trunk xorg-x11-filesystem]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-font-utils&project=Trunk xorg-x11-font-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-fonts&project=Trunk xorg-x11-fonts]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-meego-configs&project=Trunk xorg-x11-meego-configs]
|ulf
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-bigreqsproto&project=Trunk xorg-x11-proto-bigreqsproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-compositeproto&project=Trunk xorg-x11-proto-compositeproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-damageproto&project=Trunk xorg-x11-proto-damageproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-dmxproto&project=Trunk xorg-x11-proto-dmxproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-dri2proto&project=Trunk xorg-x11-proto-dri2proto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-evieext&project=Trunk xorg-x11-proto-evieext]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fixesproto&project=Trunk xorg-x11-proto-fixesproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fontcacheproto&project=Trunk xorg-x11-proto-fontcacheproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-fontsproto&project=Trunk xorg-x11-proto-fontsproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-glproto&project=Trunk xorg-x11-proto-glproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-inputproto&project=Trunk xorg-x11-proto-inputproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-kbproto&project=Trunk xorg-x11-proto-kbproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-randrproto&project=Trunk xorg-x11-proto-randrproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-recordproto&project=Trunk xorg-x11-proto-recordproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-renderproto&project=Trunk xorg-x11-proto-renderproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-resourceproto&project=Trunk xorg-x11-proto-resourceproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-scrnsaverproto&project=Trunk xorg-x11-proto-scrnsaverproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-trapproto&project=Trunk xorg-x11-proto-trapproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-videoproto&project=Trunk xorg-x11-proto-videoproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xcmiscproto&project=Trunk xorg-x11-proto-xcmiscproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xextproto&project=Trunk xorg-x11-proto-xextproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86bigfontproto&project=Trunk xorg-x11-proto-xf86bigfontproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86dgaproto&project=Trunk xorg-x11-proto-xf86dgaproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86driproto&project=Trunk xorg-x11-proto-xf86driproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86miscproto&project=Trunk xorg-x11-proto-xf86miscproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86rushproto&project=Trunk xorg-x11-proto-xf86rushproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xf86vidmodeproto&project=Trunk xorg-x11-proto-xf86vidmodeproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xineramaproto&project=Trunk xorg-x11-proto-xineramaproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xproto&project=Trunk xorg-x11-proto-xproto]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-proto-xproxymanagementprotocol&project=Trunk xorg-x11-proto-xproxymanagementprotocol]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-server&project=Trunk xorg-x11-server]
|pli1
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-server-utils&project=Trunk xorg-x11-server-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-twm&project=Trunk xorg-x11-twm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-util-macros&project=Trunk xorg-x11-util-macros]
|pli1,xyl
|devel:x11:Trunk
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils&project=Trunk xorg-x11-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-iceauth&project=Trunk xorg-x11-utils-iceauth]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-rgb&project=Trunk xorg-x11-utils-rgb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-sessreg&project=Trunk xorg-x11-utils-sessreg]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xcmsdb&project=Trunk xorg-x11-utils-xcmsdb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xdpyinfo&project=Trunk xorg-x11-utils-xdpyinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xdriinfo&project=Trunk xorg-x11-utils-xdriinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xev&project=Trunk xorg-x11-utils-xev]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xfd&project=Trunk xorg-x11-utils-xfd]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xfontsel&project=Trunk xorg-x11-utils-xfontsel]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xgamma&project=Trunk xorg-x11-utils-xgamma]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xhost&project=Trunk xorg-x11-utils-xhost]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xinput&project=Trunk xorg-x11-utils-xinput]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsatoms&project=Trunk xorg-x11-utils-xlsatoms]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsclients&project=Trunk xorg-x11-utils-xlsclients]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xlsfonts&project=Trunk xorg-x11-utils-xlsfonts]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xmodmap&project=Trunk xorg-x11-utils-xmodmap]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xprop&project=Trunk xorg-x11-utils-xprop]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrandr&project=Trunk xorg-x11-utils-xrandr]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrdb&project=Trunk xorg-x11-utils-xrdb]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xrefresh&project=Trunk xorg-x11-utils-xrefresh]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xset&project=Trunk xorg-x11-utils-xset]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xsetroot&project=Trunk xorg-x11-utils-xsetroot]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xvinfo&project=Trunk xorg-x11-utils-xvinfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-utils-xwininfo&project=Trunk xorg-x11-utils-xwininfo]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xauth&project=Trunk xorg-x11-xauth]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xbitmaps&project=Trunk xorg-x11-xbitmaps]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xinit&project=Trunk xorg-x11-xinit]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xkb-utils&project=Trunk xorg-x11-xkb-utils]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xorg-x11-xtrans-devel&project=Trunk xorg-x11-xtrans-devel]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xterm&project=Trunk xterm]
|xyl
|
|-
|[http://build.meego.com/package/show?package=xz&project=Trunk xz]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=xz-libs-x86&project=Trunk xz-libs-x86]
|jsmoeller
|
|-
|[http://build.meego.com/package/show?package=yasm&project=Trunk yasm]
|austin
|devel:base
|-
|[http://build.meego.com/package/show?package=yelp&project=Trunk yelp]
|xiaoqiang,quanxianwang
|
|-
|[http://build.meego.com/package/show?package=yum&project=Trunk yum]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=yum-metadata-parser&project=Trunk yum-metadata-parser]
|
|
|-
|[http://build.meego.com/package/show?package=yum-utils&project=Trunk yum-utils]
|xiaoqiang
|devel:packagemanagement
|-
|[http://build.meego.com/package/show?package=zenity&project=Trunk zenity]
|
|
|-
|[http://build.meego.com/package/show?package=zile&project=Trunk zile]
|
|
|-
|[http://build.meego.com/package/show?package=zip&project=Trunk zip]
|yyang,xiaoqiang
|
|-
|[http://build.meego.com/package/show?package=zlib&project=Trunk zlib]
|yyin2
|
|-
|[http://build.meego.com/package/show?package=zlib-x86&project=Trunk zlib-x86]
|jsmoeller
|devel:base
|-
|[http://build.meego.com/package/show?package=zsh&project=Trunk zsh]
|nashif
|
|-
|[http://build.meego.com/package/show?package=zvbi&project=Trunk zvbi]
|
|
|-
|[http://build.meego.com/package/show?package=zypper&project=Trunk zypper]
|xiaoqiang
|devel:packagemanagement
|-
|}

[[Category:Packaging]]

Taking screenshots on MeeGo

2011-04-20T18:23:34Z

Pmccarty: clarification

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

* Make sure you have an active internet connection.
* Open the Terminal. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> with the command

<code># zypper in ImageMagick</code>

* Exit the root environment by typing <tt>exit</tt>.
* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot.

<code>$ import filename.png</code>

* Return to the X session by typing Alt+F2
* Click (or touch) the display and wait a few seconds
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-20T18:22:24Z

Pmccarty: clarify directions for becoming root user

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

* Make sure you have an active internet connection.
* Open the Terminal. Become root by typing <tt>su</tt>. The default password is "meego".
* Install <tt>ImageMagick</tt> with the command

<code># zypper in ImageMagick</code>

* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot.

<code>$ import filename.png</code>

* Return to the X session by typing Alt+F2
* Click (or touch) the display and wait a few seconds
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-20T18:19:10Z

Pmccarty: add more details

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

* Make sure you have an active internet connection.
* Open the Terminal. As root user, install <tt>ImageMagick</tt> with the command

<code># zypper in ImageMagick</code>

* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user. By default, the user is "meego" and the password is "meego".
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot.

<code>$ import filename.png</code>

* Return to the X session by typing Alt+F2
* Click (or touch) the display and wait a few seconds
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-19T22:01:11Z

Pmccarty: typo

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

* Make sure you have an active internet connection.
* Open the Terminal. As root user, install <tt>ImageMagick</tt> with the command

<code># zypper in ImageMagick</code>

* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal user.
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot.

<code>$ import filename.png</code>

* Return to the X session by typing Alt+F2
* Click (or touch) the display and wait a few seconds
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-19T21:52:30Z

Pmccarty: switch to using bullets instead of numbered lists

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

* Make sure you have an active internet connection.
* Open the Terminal. As root user, install <tt>ImageMagick</tt> with the command

<code># zypper in ImageMagick</code>

* Open applications, etc. until your display is ready for a screenshot.
* Switch to the first virtual terminal by typing Ctrl+Alt+F1
* Log in as a normal, unprivileged user.
* Navigate to the directory in which you want to save the screenshot.
* Execute the following command, where "filename.png" is the name you want for the screenshot.

<code>$ import filename.png</code>

* Return to the X session by typing Alt+F2
* Click (or touch) the display and wait a few seconds
* Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
* That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-19T21:50:25Z

Pmccarty: /* MeeGo UX */

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

# Make sure you have an active internet connection.
# Open the Terminal. As root user, install <tt>ImageMagick</tt> with the command <code>zypper in ImageMagick</code>
# Open applications, etc. until your display is ready for a screenshot.
# Switch to the first virtual terminal by typing Ctrl+Alt+F1
# Log in as a normal, unprivileged user.
# Navigate to the directory in which you want to save the screenshot.
# Execute the following command: <code>import filename.png</code> "filename.png" is the name you want for the screenshot.
# Return to the X session by typing Alt+F2
# Click (or touch) the display and wait a few seconds
# Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
# That's it! Your screenshot can be found in the current directory.

Taking screenshots on MeeGo

2011-04-19T21:48:18Z

Pmccarty: add howto for taking native MeeGo screenshots

== MeeGo Netbook UX ==

TODO

== MeeGo UX ==

Currently, there is no *easy* method of taking native screenshots with MeeGo UX, but the command-line approach is as follows:

# Make sure you have an active internet connection.
# Open the Terminal. As root user, install <tt>ImageMagick</tt> with this command:

# zypper in ImageMagick

# Open applications, etc. until your display is ready for a screenshot.
# Switch to the first virtual terminal by typing Ctrl+Alt+F1
# Log in as a normal, unprivileged user.
# Navigate to the directory in which you want to save the screenshot.
# Execute the following command, where "filename.png" is the name you want for the screenshot.

$ import filename.png

# Return to the X session by typing Alt+F2
# Click (or touch) the display and wait a few seconds
# Switch back to the virtual terminal (Ctrl+Alt+F1), and verify that the 'import' command completed without errors.
# That's it! Your screenshot can be found in the current directory.

Using Transifex

2011-04-19T21:26:33Z

Pmccarty: revise the list of steps for translation

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' A few months ago, the MeeGo Transifex site was privately hosted at http://translate.moblin.org, but this site is no longer used. Please update your bookmarks to current site, https://meego.transifex.net/.

#Once approved for a language team, choose a MeeGo release you would like to translate from the [https://meego.transifex.net/ MeeGo Hub]. The latest release will be labeled and will likely receive the most attention.
#The next page displays a large list of translation statistics for all MeeGo language teams. Click on the language code for your team to see all of the resources available for translation.
#If translation has already started for a particular resource, simply click on the resource name to continue translation, or revise existing translations.
#If no translation exists yet for a particular resource, it will be listed at the bottom of the page. Follow the link for the desired resource to translate. Now you have landed on the resource page. Click "Add translation", choose your language from the dropdown menu, and click "Translate Online".
#After you are finished translating, remember to click the "Save and Exit" button near the page bottom.
#Now your translations are available for MeeGo developers to integrate into the distribution.

'''Note:''' If you are finished translating, be sure to unlock the translation so others on your team can work on it.

'''Note:''' Transifex lets you download translation resources so you can translate locally instead of through the web interface. For MeeGo Netbook UX PO files, we highly recommend using PO Edit to translate them. For MeeGo UX TS files, the Qt Linguist tool is recommended. There are other applications that also get the job done. Lokalize (formerly known as KBabel) is a program from the KDE project that works on Linux. The biggest plus with this program is the translation memory. You can load other translations, such as the Gnome translations, in the memory and Lokalize suggests the translations when a similar translation exists. Very handy for consistency.

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Using Transifex

2011-04-19T21:06:43Z

Pmccarty: update one more hub link

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' A few months ago, the MeeGo Transifex site was privately hosted at http://translate.moblin.org, but this site is no longer used. Please update your bookmarks to current site, https://meego.transifex.net/.

#Once approved for a language team, choose a project from the [https://meego.transifex.net/ MeeGo Hub]. We will use bisho as an example. Click master under the "Project Component" heading.
#If your language does not show in the list, you will need to download the English template, translate, and then submit as a new language. To do that, look under the heading “Translation Files” for the “Source File” followed by po/bisho.pot. This is the template you use. Click the little icon with the green arrow to download it.
#Otherwise, if you see your language in the list, check the percentage of translation. If it is 100%, it has already been translated. If you are reviewing the translation, then click the second icon (with the little green downward pointing arrow). Be sure to lock the file so others know that it is in use. Review and edit the file, and then upload, using the icon with the upward pointing green arrow. Be sure to unlock the file after uploading it.
#For MeeGo Netbook UX po files, we highly recommend using PO Edit to translate the file.

However, there are other applications that also get the job done. Lokalize (formerly known as KBabel) is a program from the KDE project that works on Linux. The biggest plus with this program is the translation memory. You can load other translations, such as the Gnome translations, in the memory and Lokalize suggests the translations when a similar translation exists. Very handy for consistency.

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Using Transifex

2011-04-19T21:03:32Z

Pmccarty: more revisions

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' A few months ago, the MeeGo Transifex site was privately hosted at http://translate.moblin.org, but this site is no longer used. Please update your bookmarks to current site, https://meego.transifex.net/.

#Once approved for a language team, choose a project from the [http://meego.transifex.net MeeGo Hub]. We will use bisho as an example. Click master under the "Project Component" heading.
#If your language does not show in the list, you will need to download the English template, translate, and then submit as a new language. To do that, look under the heading “Translation Files” for the “Source File” followed by po/bisho.pot. This is the template you use. Click the little icon with the green arrow to download it.
#Otherwise, if you see your language in the list, check the percentage of translation. If it is 100%, it has already been translated. If you are reviewing the translation, then click the second icon (with the little green downward pointing arrow). Be sure to lock the file so others know that it is in use. Review and edit the file, and then upload, using the icon with the upward pointing green arrow. Be sure to unlock the file after uploading it.
#For MeeGo Netbook UX po files, we highly recommend using PO Edit to translate the file.

However, there are other applications that also get the job done. Lokalize (formerly known as KBabel) is a program from the KDE project that works on Linux. The biggest plus with this program is the translation memory. You can load other translations, such as the Gnome translations, in the memory and Lokalize suggests the translations when a similar translation exists. Very handy for consistency.

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Using Transifex

2011-04-19T21:00:36Z

Pmccarty: remove outdated information

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' We have just recently moved from a "private" hosting of MeeGo po files (http://translate.moblin.org) to our new publicly-hosted site https://meego.transifex.net/.

#Once approved for a language team, choose a project from the [http://meego.transifex.net MeeGo Hub]. We will use bisho as an example. Click master under the "Project Component" heading.
#If your language does not show in the list, you will need to download the English template, translate, and then submit as a new language. To do that, look under the heading “Translation Files” for the “Source File” followed by po/bisho.pot. This is the template you use. Click the little icon with the green arrow to download it.
#Otherwise, if you see your language in the list, check the percentage of translation. If it is 100%, it has already been translated. If you are reviewing the translation, then click the second icon (with the little green downward pointing arrow). Be sure to lock the file so others know that it is in use. Review and edit the file, and then upload, using the icon with the upward pointing green arrow. Be sure to unlock the file after uploading it.
#For MeeGo Netbook UX po files, we highly recommend using PO Edit to translate the file.

However, there are other applications that also get the job done. Lokalize (formerly known as KBabel) is a program from the KDE project that works on Linux. The biggest plus with this program is the translation memory. You can load other translations, such as the Gnome translations, in the memory and Lokalize suggests the translations when a similar translation exists. Very handy for consistency.

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Using Transifex

2011-04-19T20:59:38Z

Pmccarty: revisions

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date translation resource, translate, and post it back to the project.

'''Note:''' We have just recently moved from a "private" hosting of MeeGo po files (http://translate.moblin.org) to our new publicly-hosted site https://meego.transifex.net/.

'''Note:''' We assume that you are familiar with po files, Linux, and character encoding. Most of the MeeGo Netbook UX are po files that are encoded with UTF-8. Please be sure that the Content-Type in the header of these PO files is "UTF-8." Going forward, MeeGo is also [http://qt.gitorious.org/qt/pages/QtLocalization using qt] and we are just now starting to understand what that means. Join the mailing list and attend the L10N IRC meetings to keep up with the latest. Transifex will indeed [http://wiki.meego.com/Transifex_Roadmap support qt] very soon.

#Once approved for a language team, choose a project from the [http://meego.transifex.net MeeGo Hub]. We will use bisho as an example. Click master under the "Project Component" heading.
#If your language does not show in the list, you will need to download the English template, translate, and then submit as a new language. To do that, look under the heading “Translation Files” for the “Source File” followed by po/bisho.pot. This is the template you use. Click the little icon with the green arrow to download it.
#Otherwise, if you see your language in the list, check the percentage of translation. If it is 100%, it has already been translated. If you are reviewing the translation, then click the second icon (with the little green downward pointing arrow). Be sure to lock the file so others know that it is in use. Review and edit the file, and then upload, using the icon with the upward pointing green arrow. Be sure to unlock the file after uploading it.
#For MeeGo Netbook UX po files, we highly recommend using PO Edit to translate the file.

However, there are other applications that also get the job done. Lokalize (formerly known as KBabel) is a program from the KDE project that works on Linux. The biggest plus with this program is the translation memory. You can load other translations, such as the Gnome translations, in the memory and Lokalize suggests the translations when a similar translation exists. Very handy for consistency.

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Using Transifex

2011-04-19T20:58:26Z

Pmccarty: link to secure Transifex pages

Go to https://meego.transifex.net/ and register. Once you have done that, select a language team to join. The lead for that team will then contact you and, if you agree on process for that language, you will be approved for that language team. If you don't see a team for your language, please consider starting it and being the lead, at least until you have critical mass.

Ideally, a language team should have a lead, at least 2 translators, and at least two editors/reviewers. It is essential that the same person that translates does not also review and approve their translation!

Once you've joined a language team, you can start translating! Transifex makes it easy for you to get the most up-to-date po file, translate, and post it back to the project.

'''Note:''' We have just recently moved from a "private" hosting of MeeGo po files (http://translate.moblin.org) to our new publicly-hosted site https://meego.transifex.net/.

'''Note:''' We assume that you are familiar with po files, Linux, and character encoding. Most of the MeeGo Netbook UX are po files that are encoded with UTF-8. Please be sure that the Content-Type in the header of these PO files is "UTF-8." Going forward, MeeGo is also [http://qt.gitorious.org/qt/pages/QtLocalization using qt] and we are just now starting to understand what that means. Join the mailing list and attend the L10N IRC meetings to keep up with the latest. Transifex will indeed [http://wiki.meego.com/Transifex_Roadmap support qt] very soon.

#Once approved for a language team, choose a project from the [http://meego.transifex.net MeeGo Hub]. We will use bisho as an example. Click master under the "Project Component" heading.
#If your language does not show in the list, you will need to download the English template, translate, and then submit as a new language. To do that, look under the heading “Translation Files” for the “Source File” followed by po/bisho.pot. This is the template you use. Click the little icon with the green arrow to download it.
#Otherwise, if you see your language in the list, check the percentage of translation. If it is 100%, it has already been translated. If you are reviewing the translation, then click the second icon (with the little green downward pointing arrow). Be sure to lock the file so others know that it is in use. Review and edit the file, and then upload, using the icon with the upward pointing green arrow. Be sure to unlock the file after uploading it.
#For MeeGo Netbook UX po files, we highly recommend using PO Edit to translate the file.

However, there are other applications that also get the job done. Lokalize (formerly known as KBabel) is a program from the KDE project that works on Linux. The biggest plus with this program is the translation memory. You can load other translations, such as the Gnome translations, in the memory and Lokalize suggests the translations when a similar translation exists. Very handy for consistency.

== Starting a Translation ==

For those of you familiar with PO Edit and editing po files, skip the next 3 steps.
#Open the bisho.pot file in PO Edit. In the Settings dialog, be sure to put your email address in the file heading (under “Last-Translator”) so we know who did the work and you get the recognition for doing it! Also, please be sure that the Content-Type in the header is "UTF-8." Make sure to enter this in the plural field to avoid corruptions and losing your work when you save: nplurals=2; plural=n!=1;
#Save the settings you just entered.
#Notice that there is a English string and right below it is msgstr “”. Put your translation of the English string inside those quotes.
#You can name your new PO whatever you like on your local drive, but it’s better to use the same name as the file in Transifex for easy identification when you want to upload it back.
#Go back to meego.transifex.net and go to the Bisho project.
#Scroll down until you see your language. (If it does not appear in the list, you will need to click "Add a New Translation." See below.)
#Select the last icon in the row of icons next to your language (the icon has a pencil in it and the mouse-over says "Submit a translation for po/xxx.po.")
#Use the “Browse” button to find your local file and select it.
#Click Send. If all goes well, you will see a message at the top of the screen that the po file was added successfully. You will also see your file appear in the list with the percentage of translation.
#If you have any problems, send the issue to the mailing list.

== Add a New Translation ==

If you are adding a new language for the first time to a project, click Add a new translation. The information that appears is pretty self-explanatory, but it is important to remember the following:

*Use the “Browse” button to find your local po file and select it.
*Ignore the "Select the target file" drop-down list, and enter "po/<languagecode>.po" in the "or enter it here" box.
*Finally, add some message that details what you did.
*Click Send. if all goes well, you will see a message at the top of the screen that the po file was added successfully.

[[Category:Localization]]

Localization

2011-04-19T20:55:43Z

Pmccarty: add redirect for "Localization"

#REDIRECT [[Localization team]]

Quality/Bugtriage

2011-03-01T18:27:36Z

Pmccarty: /* MeeGo Bug Triage Team */

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report completeness
** Analyze and assign bug to proper component
** Assign bug to proper bug owner
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Resolve obvious invalid, duplication, won’t fix bugs etc.

* Bug Triage Team
** A small team works on bug triage, could be experienced developer, distro engineer or QA
** Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]].

== Bug Triage Process ==
* Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
* Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
* Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
* Bug assignees accept bug reports by setting target milestones for triaged bug reports
* [http://meego.com/about/governance/program-office Program Managers] host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:
[[File:bug_triage_process.jpg]]

== MeeGo Bug Triage Guide ==
Check the [http://wiki.meego.com/Quality/Bugtriage_Guide Triage Guide] that explains good practices when triaging bug reports.

== MeeGo Bug Triage Team ==
{|cellspacing="0" border="1"
!|MeeGo Bug Triage Team
!|Member
|-
| MeeGo Core OS Triage || [http://meego.com/users/jerry Jerry Yu], Peter Zhu, [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ttoropainen Tommi Toropainen], [http://meego.com/users/juhanitaipale Juhani Taipale], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/mikikone Mika Ikonen], [http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/pekoski Petri Koski], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster], [http://meego.com/users/pmccarty Patrick McCarty]
|-
| MeeGo SDK Triage || TBD
|}

=== MeeGo Bug Triage Meetings ===

* MeeGo Core Bug Triage
** Time: Every Monday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** Time: Every Thursday at 12:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Handset Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
** Time: TBD
* MeeGo Translation Bug Triage
** Time: TBD
* MeeGo SDK Bug Triage
** Time: TBD
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]

Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net].

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

* [[CoreBugTriageMinutesArchive|MeeGo Core Bug Triage Meeting Minutes Archive]]
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]]
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]]

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo!

== Other references ==
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]

Quality/Bugtriage

2011-03-01T18:27:02Z

Pmccarty: /* MeeGo Bug Triage Team */ add myself to translation triage team

== Bug Triage Definition ==
* Bug Triage is a process to:
** Ensure bug report completeness
** Analyze and assign bug to proper component
** Assign bug to proper bug owner
** Set appropriate bug priority
** Adjust bug severity properly (initially set by bug reporter)
** Resolve obvious invalid, duplication, won’t fix bugs etc.

* Bug Triage Team
** A small team works on bug triage, could be experienced developer, distro engineer or QA
** Triage team members are expected to contribute significant time to bug triage

Please share your triaging knowledge by adding/editing [[Quality/Bugtriage_Stock_Answers | MeeGo Bug Triage Stock Answers]].

== Bug Triage Process ==
* Triage new incoming bug reports timely by each triage team (from twice a week to daily triage).
* Triage team members in each triage team could have different focus, such as IA arch bugs, ARM bugs or specific applications etc.
* Each triage team meet on IRC weekly to discuss controversial bug reports and any open reports
* Bug assignees accept bug reports by setting target milestones for triaged bug reports
* [http://meego.com/about/governance/program-office Program Managers] host bug report scrub meetings to discuss bug reports which do not have a target milestone set

Triage Process Flow as follows:
[[File:bug_triage_process.jpg]]

== MeeGo Bug Triage Guide ==
Check the [http://wiki.meego.com/Quality/Bugtriage_Guide Triage Guide] that explains good practices when triaging bug reports.

== MeeGo Bug Triage Team ==
{|cellspacing="0" border="1"
!|MeeGo Bug Triage Team
!|Member
|-
| MeeGo Core OS Triage || [http://meego.com/users/jerry Jerry Yu], Peter Zhu, [http://meego.com/users/shuangeeer Yanshuang Zheng], [http://meego.com/users/ttoropainen Tommi Toropainen], [http://meego.com/users/juhanitaipale Juhani Taipale], [http://meego.com/users/jarnoteivas Jarno Teivas], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Handset UX Triage || Fan Zhao, Cathy Li, [http://meego.com/users/mikikone Mika Ikonen], [http://meego.com/users/jylha Petri Jylha], [http://meego.com/users/pekoski Petri Koski], [http://meego.com/users/ceferron Chris Ferron], [http://meego.com/users/iekku Iekku Huttunen]
|-
| MeeGo Netbook UX Triage || [http://meego.com/users/lingyu Ling Yu], Daniel Tao, [http://meego.com/users/yanglei Lei Yang], [http://meego.com/users/rossburton Ross Burton]
|-
| MeeGo IVI Triage || [http://meego.com/users/shuangeeer Yanshuang Zheng]
|-
| MeeGo Translation Triage || [http://meego.com/users/margie Margie Foster] [http://meego.com/users/pmccarty Patrick McCarty]
|-
| MeeGo SDK Triage || TBD
|}

=== MeeGo Bug Triage Meetings ===

* MeeGo Core Bug Triage
** Time: Every Monday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
** Time: Every Thursday at 12:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Handset Bug Triage
** Time: Every Wednesday at 07:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo Netbook Bug Triage
** Time: Every Tuesday at 13:00 [http://www.timeanddate.com/worldclock/converter.html UTC]
* MeeGo IVI Bug Triage
** Time: TBD
* MeeGo Translation Bug Triage
** Time: TBD
* MeeGo SDK Bug Triage
** Time: TBD
* MCTS Bug Triage
** Time: Every Wednesday at 08:00 [http://www.timeanddate.com/worldclock/converter.html UTC]

Those meetings take place in the IRC channel'''#meego-meeting''' on [http://freenode.net irc.freenode.net].

To discuss MeeGo bug triaging at any time feel free to visit the IRC channel '''#meego-bugs''' on [http://freenode.net irc.freenode.net].

* [[CoreBugTriageMinutesArchive|MeeGo Core Bug Triage Meeting Minutes Archive]]
* [[HandsetBugTriageMinutesArchive|MeeGo Handset Bug Triage Meeting Minutes Archive]]
* [[NetbookBugTriageMinutesArchive|MeeGo Netbook Bug Triage Meeting Minutes Archive]]

=== Getting involved ===

Anyone can sign up for the triage team and start helping (see the [[Quality/Bugtriage_Guide|Triage Guide]] for information and steps). Just send an email to the [http://lists.meego.com/listinfo/meego-qa meego-qa mailing list] to get involved in. Thanks for your contribution to MeeGo!

== Other references ==
[[Quality/How_To_Report_Bugs|How to report MeeGo bugs?]]

SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux

2011-02-08T22:24:47Z

Pmccarty: /* Add the repository public key */ missed one typo

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]
This page describes how to install and configure the MeeGo 1.1 SDK on your Linux development system.

== Prerequisites ==

* '''Hardware:''' Any reasonably modern hardware, such as 32-bit Intel Atom or Intel Core 2 CPU. '''To use QEMU''' to run MeeGo in a virtual machine your system must have support for ''Virtualization Technology'' (VT). See the [[SDK/Docs/1.1/MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration]] page for details.
* '''Software:''' The MeeGo 1.1 SDK has been validated on 32-bit versions of [https://fedoraproject.org/en/index Fedora 12], [[https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 9.10], and [http://www.ubuntu.com/ Ubuntu 10.04 LTS]. For support status and issues using other host OS's see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Root privileges:''' To install the SDK you will need to have root privileges. Commands that require root privileges are prefaced with "sudo". For convenience, you may wish to setup "sudo" capabilities to easily switch between root and normal user privileges (see [http://www.gratisoft.us/sudo/sudo.man.html sudoers manpage].)
* '''Commands:''' Terminal commands are prefaced with "$". Do not enter $ when entering the commands in your terminal.

== Configuring distributions package manager ==

=== On Ubuntu or Debian ===

==== Add the repo ====

Add the following line to <code>/etc/apt/sources.list.d/meego-sdk.list</code>. Replace ${distribution}/${version} with one of the following: "debian/5.0", "ubuntu/09.10", "ubuntu/10.04" or "ubuntu/10.10".

deb http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/ /

==== Add the repository public key ====

$ gpg --keyserver pgpkeys.mit.edu --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

'''Note:''' The keyserver used above is currently unresponsive. As a workaround, you may choose to use a different, trusted keyserver. For example:

$ gpg --keyserver pool.sks-keyservers.net --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

==== Update the packages database ====

$ sudo apt-get update

==== Verify repo correctness ====

To check that the MeeGo repository has been correctly added, run the following command. The details of the MADDE package should be printed.

$ apt-cache policy madde

=== On Fedora ===

==== Add the repo ====

Add the MeeGo SDK yum repository. Replace ${distribution}/${version} with one of the following: "fedora/12" or "fedora/13".

$ cd /etc/yum.repos.d/
$ sudo wget http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

==== Install the signing key ====

$ sudo rpm --import http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/repodata/repomd.xml.key

==== Update the packages database ====

$ sudo yum update

=== On MeeGo ===

To add the MeeGo SDK repository on a system running MeeGo, run the following command. Replace ${distribution}/${version} with one of the following values: "meego/1.1" or "meego/trunk".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

=== On openSUSE ===

To add the MeeGo repository, run the following command. Replace ${distribution}/${version} with one of the following values: "opensuse/11.2" or "opensuse/11.3".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

== Installing the MeeGo SDK ==
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk</pre>
</li>
</ul>

'''For ARM only:'''
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-armv7l</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-armv7l</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-armv7l</pre>
</li>
</ul>

'''For IA32 only:'''http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-ia32</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-ia32</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-ia32</pre>
</li>
</ul>

== Install MeeGo Target ==
A ''Target'' is used to build programs using the MeeGo toolchain and libraries (sysroot). It is downloaded as a large (~250MB) .bz2 file using the commands below. MADDE (MeeGo Application Develop and Debug Environment ([http://wiki.maemo.org/MADDE background])) is a tool that assists in the download and installation of the Target. "mad-admin" is the MADDE command-line tool. You can install multiple Targets and switch easily between them in Qt Creator (described later).

=== Determine the target you want to use ===

Run the command below. The available targets will be listed under the "Targets:" heading.

$ sudo mad-admin list

Some hints about the target prefixes:

* ''meego-core-armv7l'': Build applications for ARM handheld devices (such as N900)
* ''meego-handset-ia32'': Build applications for x86 handheld devices (such as Aava)
* ''meego-netbook-ia32'': Build applications for x86 netbooks.

=== Create the target ===

Run the command below. Replace <target> with the target you determined in the previous step. Note that the <code>-f</code> flag instructs MADDE to download the Target tarball (bz2) first.

$ sudo mad-admin create -f <target>

If you encounter problems, check the [[MeeGo_SDK_Troubleshooting#General_SDK_Errors|troubleshooting page]].

=== Verify target installation ===

To check that the target has been installed correctly, run the following. Replace <target> with the same value used in the previous step.

$ mad -t <target> pscreate -t qt-simple qthello
$ cd qthello
$ mad -t <target> qmake
$ mad -t <target> make

Note: Running qmake will print "-unix is deprecated". This is not an error with the compilation. You can safely ignore this for now.

=== Verify correct build ===

To check that the qt-simple application is created for the correct target, run the following command, and verify the output.

$ file build/qthello

== Install MeeGo Runtime ==
A ''Runtime'' is the MeeGo OS image that is run with QEMU when debugging applications on your host system. It is not required if you develop against real hardware running MeeGo. It is downloaded as a large (~650MB) .bz2 file using MADDE. The Runtime is not needed until you have finished configuring Qt Creator. However, as this step may take some time, it is recommended to start it now so that it can proceed in the background while you continue following the steps on this page.

See [http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes Downloading a Runtime and Using QEMU]

== Configuring Qt Creator to use the MeeGo toolchain(s) ==

Start Qt Creator by selecting '''Applications''' > '''Programming''' > '''Qt Creator'''.

Configure Qt Creator to use the MeeGo toolchain(s):
# Go to '''Tools''' > '''Options''' > '''Qt4''' > '''Qt Versions'''.
# On the right side of the '''Qt Versions''' view, click on the plus sign button to add a new version.
#: A blank, new version appears in the '''Qt Versions''' view.
# On the '''Version Name''' line, specify a name for the new version.
# On the '''qmake location''' line, specify a qmake location for the new version. The toolchain installs by default to <code>usr/lib/madde/linux-i686/targets/<target>/bin/qmake</code>.
# Click '''Rebuild''', '''Apply''' and '''OK'''.

[[File:Qt Creator adding MeeGo toolchains.png|frame|none|Adding the MeeGo toolchain(s) in Qt Creator]]

=== Using the MeeGo SDK Qt version ===

It is also possible to use Qt Creator without a MeeGo toolchain. This option can be useful if you don't need to cross-compile your software: for example, if you are doing QML development with no use of C++.

The steps are the same as above, but the '''qmake location''' is set to the <code>qmake</code> installed with the meego-sdk-qt libraries. The usual location for this on Linux is:

$ /opt/meego/meego-sdk-qt/bin/qmake

Note: On Ubuntu 10.10, you may need to install g++ in order for this step to work. If necessary, do this:

$ sudo apt-get install g++

== Developing with the SDK ==

To start developing with the MeeGo SDK, the [[SDK/Docs/1.1/Creating_Hello_World|hello world tutorial]] is a good starting point.

This tutorial covers how to start a project, package it, and deploy it to a device (either a real device, or a QEMU runtime set up through MADDE).

== Removing components ==

=== On Ubuntu ===

To remove installed components, run:
$ sudo apt-get remove --purge meego-sdk-qtcreator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu meego-sdk-qt

To remove dependencies related to installed components, run:
$ sudo apt-get autoremove

To remove MADDE directory (it is not automatically removed when "madde" package is uninstalled):
$ sudo rm -rf /usr/lib/madde

To remove the packages from your local repository (<code>/var/cache/apt/archives/</code>), run:
$ sudo apt-get clean

=== On Fedora ===

To remove installed components, run:
$ sudo yum remove meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

=== On openSUSE / MeeGo ===

To remove installed components, run:
$ sudo zypper remove -u meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

== Another language version of this page ==

* [[SDK/Docs/1.1/Memulai_dengan_SDK_MeeGo_untuk_Linux|Memulai dengan SDK Meego untuk Linux - Bahasa Indonesia]]
* [[SDK/Docs/1.1/在Linux平台开发进行MeeGo_SDK开发|在Linux平台进行MeeGo_SDK开发 - 简体中文]]

SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux

2011-02-08T22:24:32Z

Pmccarty: /* Add the repository public key */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]
This page describes how to install and configure the MeeGo 1.1 SDK on your Linux development system.

== Prerequisites ==

* '''Hardware:''' Any reasonably modern hardware, such as 32-bit Intel Atom or Intel Core 2 CPU. '''To use QEMU''' to run MeeGo in a virtual machine your system must have support for ''Virtualization Technology'' (VT). See the [[SDK/Docs/1.1/MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration]] page for details.
* '''Software:''' The MeeGo 1.1 SDK has been validated on 32-bit versions of [https://fedoraproject.org/en/index Fedora 12], [[https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 9.10], and [http://www.ubuntu.com/ Ubuntu 10.04 LTS]. For support status and issues using other host OS's see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Root privileges:''' To install the SDK you will need to have root privileges. Commands that require root privileges are prefaced with "sudo". For convenience, you may wish to setup "sudo" capabilities to easily switch between root and normal user privileges (see [http://www.gratisoft.us/sudo/sudo.man.html sudoers manpage].)
* '''Commands:''' Terminal commands are prefaced with "$". Do not enter $ when entering the commands in your terminal.

== Configuring distributions package manager ==

=== On Ubuntu or Debian ===

==== Add the repo ====

Add the following line to <code>/etc/apt/sources.list.d/meego-sdk.list</code>. Replace ${distribution}/${version} with one of the following: "debian/5.0", "ubuntu/09.10", "ubuntu/10.04" or "ubuntu/10.10".

deb http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/ /

==== Add the repository public key ====

$ gpg --keyserver pgpkeys.mit.edu --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

'''Note:''' This keyserver used above is currently unresponsive. As a workaround, you may choose to use a different, trusted keyserver. For example:

$ gpg --keyserver pool.sks-keyservers.net --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

==== Update the packages database ====

$ sudo apt-get update

==== Verify repo correctness ====

To check that the MeeGo repository has been correctly added, run the following command. The details of the MADDE package should be printed.

$ apt-cache policy madde

=== On Fedora ===

==== Add the repo ====

Add the MeeGo SDK yum repository. Replace ${distribution}/${version} with one of the following: "fedora/12" or "fedora/13".

$ cd /etc/yum.repos.d/
$ sudo wget http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

==== Install the signing key ====

$ sudo rpm --import http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/repodata/repomd.xml.key

==== Update the packages database ====

$ sudo yum update

=== On MeeGo ===

To add the MeeGo SDK repository on a system running MeeGo, run the following command. Replace ${distribution}/${version} with one of the following values: "meego/1.1" or "meego/trunk".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

=== On openSUSE ===

To add the MeeGo repository, run the following command. Replace ${distribution}/${version} with one of the following values: "opensuse/11.2" or "opensuse/11.3".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

== Installing the MeeGo SDK ==
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk</pre>
</li>
</ul>

'''For ARM only:'''
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-armv7l</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-armv7l</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-armv7l</pre>
</li>
</ul>

'''For IA32 only:'''http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-ia32</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-ia32</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-ia32</pre>
</li>
</ul>

== Install MeeGo Target ==
A ''Target'' is used to build programs using the MeeGo toolchain and libraries (sysroot). It is downloaded as a large (~250MB) .bz2 file using the commands below. MADDE (MeeGo Application Develop and Debug Environment ([http://wiki.maemo.org/MADDE background])) is a tool that assists in the download and installation of the Target. "mad-admin" is the MADDE command-line tool. You can install multiple Targets and switch easily between them in Qt Creator (described later).

=== Determine the target you want to use ===

Run the command below. The available targets will be listed under the "Targets:" heading.

$ sudo mad-admin list

Some hints about the target prefixes:

* ''meego-core-armv7l'': Build applications for ARM handheld devices (such as N900)
* ''meego-handset-ia32'': Build applications for x86 handheld devices (such as Aava)
* ''meego-netbook-ia32'': Build applications for x86 netbooks.

=== Create the target ===

Run the command below. Replace <target> with the target you determined in the previous step. Note that the <code>-f</code> flag instructs MADDE to download the Target tarball (bz2) first.

$ sudo mad-admin create -f <target>

If you encounter problems, check the [[MeeGo_SDK_Troubleshooting#General_SDK_Errors|troubleshooting page]].

=== Verify target installation ===

To check that the target has been installed correctly, run the following. Replace <target> with the same value used in the previous step.

$ mad -t <target> pscreate -t qt-simple qthello
$ cd qthello
$ mad -t <target> qmake
$ mad -t <target> make

Note: Running qmake will print "-unix is deprecated". This is not an error with the compilation. You can safely ignore this for now.

=== Verify correct build ===

To check that the qt-simple application is created for the correct target, run the following command, and verify the output.

$ file build/qthello

== Install MeeGo Runtime ==
A ''Runtime'' is the MeeGo OS image that is run with QEMU when debugging applications on your host system. It is not required if you develop against real hardware running MeeGo. It is downloaded as a large (~650MB) .bz2 file using MADDE. The Runtime is not needed until you have finished configuring Qt Creator. However, as this step may take some time, it is recommended to start it now so that it can proceed in the background while you continue following the steps on this page.

See [http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes Downloading a Runtime and Using QEMU]

== Configuring Qt Creator to use the MeeGo toolchain(s) ==

Start Qt Creator by selecting '''Applications''' > '''Programming''' > '''Qt Creator'''.

Configure Qt Creator to use the MeeGo toolchain(s):
# Go to '''Tools''' > '''Options''' > '''Qt4''' > '''Qt Versions'''.
# On the right side of the '''Qt Versions''' view, click on the plus sign button to add a new version.
#: A blank, new version appears in the '''Qt Versions''' view.
# On the '''Version Name''' line, specify a name for the new version.
# On the '''qmake location''' line, specify a qmake location for the new version. The toolchain installs by default to <code>usr/lib/madde/linux-i686/targets/<target>/bin/qmake</code>.
# Click '''Rebuild''', '''Apply''' and '''OK'''.

[[File:Qt Creator adding MeeGo toolchains.png|frame|none|Adding the MeeGo toolchain(s) in Qt Creator]]

=== Using the MeeGo SDK Qt version ===

It is also possible to use Qt Creator without a MeeGo toolchain. This option can be useful if you don't need to cross-compile your software: for example, if you are doing QML development with no use of C++.

The steps are the same as above, but the '''qmake location''' is set to the <code>qmake</code> installed with the meego-sdk-qt libraries. The usual location for this on Linux is:

$ /opt/meego/meego-sdk-qt/bin/qmake

Note: On Ubuntu 10.10, you may need to install g++ in order for this step to work. If necessary, do this:

$ sudo apt-get install g++

== Developing with the SDK ==

To start developing with the MeeGo SDK, the [[SDK/Docs/1.1/Creating_Hello_World|hello world tutorial]] is a good starting point.

This tutorial covers how to start a project, package it, and deploy it to a device (either a real device, or a QEMU runtime set up through MADDE).

== Removing components ==

=== On Ubuntu ===

To remove installed components, run:
$ sudo apt-get remove --purge meego-sdk-qtcreator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu meego-sdk-qt

To remove dependencies related to installed components, run:
$ sudo apt-get autoremove

To remove MADDE directory (it is not automatically removed when "madde" package is uninstalled):
$ sudo rm -rf /usr/lib/madde

To remove the packages from your local repository (<code>/var/cache/apt/archives/</code>), run:
$ sudo apt-get clean

=== On Fedora ===

To remove installed components, run:
$ sudo yum remove meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

=== On openSUSE / MeeGo ===

To remove installed components, run:
$ sudo zypper remove -u meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

== Another language version of this page ==

* [[SDK/Docs/1.1/Memulai_dengan_SDK_MeeGo_untuk_Linux|Memulai dengan SDK Meego untuk Linux - Bahasa Indonesia]]
* [[SDK/Docs/1.1/在Linux平台开发进行MeeGo_SDK开发|在Linux平台进行MeeGo_SDK开发 - 简体中文]]

SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux

2011-02-08T22:22:38Z

Pmccarty: /* Add the repository public key */ add an alternate, working keyserver

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]
This page describes how to install and configure the MeeGo 1.1 SDK on your Linux development system.

== Prerequisites ==

* '''Hardware:''' Any reasonably modern hardware, such as 32-bit Intel Atom or Intel Core 2 CPU. '''To use QEMU''' to run MeeGo in a virtual machine your system must have support for ''Virtualization Technology'' (VT). See the [[SDK/Docs/1.1/MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration]] page for details.
* '''Software:''' The MeeGo 1.1 SDK has been validated on 32-bit versions of [https://fedoraproject.org/en/index Fedora 12], [[https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 9.10], and [http://www.ubuntu.com/ Ubuntu 10.04 LTS]. For support status and issues using other host OS's see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Root privileges:''' To install the SDK you will need to have root privileges. Commands that require root privileges are prefaced with "sudo". For convenience, you may wish to setup "sudo" capabilities to easily switch between root and normal user privileges (see [http://www.gratisoft.us/sudo/sudo.man.html sudoers manpage].)
* '''Commands:''' Terminal commands are prefaced with "$". Do not enter $ when entering the commands in your terminal.

== Configuring distributions package manager ==

=== On Ubuntu or Debian ===

==== Add the repo ====

Add the following line to <code>/etc/apt/sources.list.d/meego-sdk.list</code>. Replace ${distribution}/${version} with one of the following: "debian/5.0", "ubuntu/09.10", "ubuntu/10.04" or "ubuntu/10.10".

deb http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/ /

==== Add the repository public key ====

$ gpg --keyserver pgpkeys.mit.edu --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

'''Note:''' This keyserver is currently unresponsive. As a workaround, you may choose to use a different, trusted keyserver. For example:

$ gpg --keyserver pool.sks-keyservers.net --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

==== Update the packages database ====

$ sudo apt-get update

==== Verify repo correctness ====

To check that the MeeGo repository has been correctly added, run the following command. The details of the MADDE package should be printed.

$ apt-cache policy madde

=== On Fedora ===

==== Add the repo ====

Add the MeeGo SDK yum repository. Replace ${distribution}/${version} with one of the following: "fedora/12" or "fedora/13".

$ cd /etc/yum.repos.d/
$ sudo wget http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

==== Install the signing key ====

$ sudo rpm --import http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/repodata/repomd.xml.key

==== Update the packages database ====

$ sudo yum update

=== On MeeGo ===

To add the MeeGo SDK repository on a system running MeeGo, run the following command. Replace ${distribution}/${version} with one of the following values: "meego/1.1" or "meego/trunk".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

=== On openSUSE ===

To add the MeeGo repository, run the following command. Replace ${distribution}/${version} with one of the following values: "opensuse/11.2" or "opensuse/11.3".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

== Installing the MeeGo SDK ==
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk</pre>
</li>
</ul>

'''For ARM only:'''
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-armv7l</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-armv7l</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-armv7l</pre>
</li>
</ul>

'''For IA32 only:'''http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-ia32</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-ia32</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-ia32</pre>
</li>
</ul>

== Install MeeGo Target ==
A ''Target'' is used to build programs using the MeeGo toolchain and libraries (sysroot). It is downloaded as a large (~250MB) .bz2 file using the commands below. MADDE (MeeGo Application Develop and Debug Environment ([http://wiki.maemo.org/MADDE background])) is a tool that assists in the download and installation of the Target. "mad-admin" is the MADDE command-line tool. You can install multiple Targets and switch easily between them in Qt Creator (described later).

=== Determine the target you want to use ===

Run the command below. The available targets will be listed under the "Targets:" heading.

$ sudo mad-admin list

Some hints about the target prefixes:

* ''meego-core-armv7l'': Build applications for ARM handheld devices (such as N900)
* ''meego-handset-ia32'': Build applications for x86 handheld devices (such as Aava)
* ''meego-netbook-ia32'': Build applications for x86 netbooks.

=== Create the target ===

Run the command below. Replace <target> with the target you determined in the previous step. Note that the <code>-f</code> flag instructs MADDE to download the Target tarball (bz2) first.

$ sudo mad-admin create -f <target>

If you encounter problems, check the [[MeeGo_SDK_Troubleshooting#General_SDK_Errors|troubleshooting page]].

=== Verify target installation ===

To check that the target has been installed correctly, run the following. Replace <target> with the same value used in the previous step.

$ mad -t <target> pscreate -t qt-simple qthello
$ cd qthello
$ mad -t <target> qmake
$ mad -t <target> make

Note: Running qmake will print "-unix is deprecated". This is not an error with the compilation. You can safely ignore this for now.

=== Verify correct build ===

To check that the qt-simple application is created for the correct target, run the following command, and verify the output.

$ file build/qthello

== Install MeeGo Runtime ==
A ''Runtime'' is the MeeGo OS image that is run with QEMU when debugging applications on your host system. It is not required if you develop against real hardware running MeeGo. It is downloaded as a large (~650MB) .bz2 file using MADDE. The Runtime is not needed until you have finished configuring Qt Creator. However, as this step may take some time, it is recommended to start it now so that it can proceed in the background while you continue following the steps on this page.

See [http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes Downloading a Runtime and Using QEMU]

== Configuring Qt Creator to use the MeeGo toolchain(s) ==

Start Qt Creator by selecting '''Applications''' > '''Programming''' > '''Qt Creator'''.

Configure Qt Creator to use the MeeGo toolchain(s):
# Go to '''Tools''' > '''Options''' > '''Qt4''' > '''Qt Versions'''.
# On the right side of the '''Qt Versions''' view, click on the plus sign button to add a new version.
#: A blank, new version appears in the '''Qt Versions''' view.
# On the '''Version Name''' line, specify a name for the new version.
# On the '''qmake location''' line, specify a qmake location for the new version. The toolchain installs by default to <code>usr/lib/madde/linux-i686/targets/<target>/bin/qmake</code>.
# Click '''Rebuild''', '''Apply''' and '''OK'''.

[[File:Qt Creator adding MeeGo toolchains.png|frame|none|Adding the MeeGo toolchain(s) in Qt Creator]]

=== Using the MeeGo SDK Qt version ===

It is also possible to use Qt Creator without a MeeGo toolchain. This option can be useful if you don't need to cross-compile your software: for example, if you are doing QML development with no use of C++.

The steps are the same as above, but the '''qmake location''' is set to the <code>qmake</code> installed with the meego-sdk-qt libraries. The usual location for this on Linux is:

$ /opt/meego/meego-sdk-qt/bin/qmake

Note: On Ubuntu 10.10, you may need to install g++ in order for this step to work. If necessary, do this:

$ sudo apt-get install g++

== Developing with the SDK ==

To start developing with the MeeGo SDK, the [[SDK/Docs/1.1/Creating_Hello_World|hello world tutorial]] is a good starting point.

This tutorial covers how to start a project, package it, and deploy it to a device (either a real device, or a QEMU runtime set up through MADDE).

== Removing components ==

=== On Ubuntu ===

To remove installed components, run:
$ sudo apt-get remove --purge meego-sdk-qtcreator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu meego-sdk-qt

To remove dependencies related to installed components, run:
$ sudo apt-get autoremove

To remove MADDE directory (it is not automatically removed when "madde" package is uninstalled):
$ sudo rm -rf /usr/lib/madde

To remove the packages from your local repository (<code>/var/cache/apt/archives/</code>), run:
$ sudo apt-get clean

=== On Fedora ===

To remove installed components, run:
$ sudo yum remove meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

=== On openSUSE / MeeGo ===

To remove installed components, run:
$ sudo zypper remove -u meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

== Another language version of this page ==

* [[SDK/Docs/1.1/Memulai_dengan_SDK_MeeGo_untuk_Linux|Memulai dengan SDK Meego untuk Linux - Bahasa Indonesia]]
* [[SDK/Docs/1.1/在Linux平台开发进行MeeGo_SDK开发|在Linux平台进行MeeGo_SDK开发 - 简体中文]]

SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux

2011-02-08T22:09:03Z

Pmccarty: /* Configuring distributions package manager */ clean up more wiki source

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]
This page describes how to install and configure the MeeGo 1.1 SDK on your Linux development system.

== Prerequisites ==

* '''Hardware:''' Any reasonably modern hardware, such as 32-bit Intel Atom or Intel Core 2 CPU. '''To use QEMU''' to run MeeGo in a virtual machine your system must have support for ''Virtualization Technology'' (VT). See the [[SDK/Docs/1.1/MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration]] page for details.
* '''Software:''' The MeeGo 1.1 SDK has been validated on 32-bit versions of [https://fedoraproject.org/en/index Fedora 12], [[https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 9.10], and [http://www.ubuntu.com/ Ubuntu 10.04 LTS]. For support status and issues using other host OS's see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Root privileges:''' To install the SDK you will need to have root privileges. Commands that require root privileges are prefaced with "sudo". For convenience, you may wish to setup "sudo" capabilities to easily switch between root and normal user privileges (see [http://www.gratisoft.us/sudo/sudo.man.html sudoers manpage].)
* '''Commands:''' Terminal commands are prefaced with "$". Do not enter $ when entering the commands in your terminal.

== Configuring distributions package manager ==

=== On Ubuntu or Debian ===

==== Add the repo ====

Add the following line to <code>/etc/apt/sources.list.d/meego-sdk.list</code>. Replace ${distribution}/${version} with one of the following: "debian/5.0", "ubuntu/09.10", "ubuntu/10.04" or "ubuntu/10.10".

deb http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/ /

==== Add the repository public key ====

$ gpg --keyserver pgpkeys.mit.edu --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

'''Note:''' This keyserver is currently unresponsive, and this particular key may be invalid. You may skip this step, but be wary of the repo you are downloading from.

==== Update the packages database ====

$ sudo apt-get update

==== Verify repo correctness ====

To check that the MeeGo repository has been correctly added, run the following command. The details of the MADDE package should be printed.

$ apt-cache policy madde

=== On Fedora ===

==== Add the repo ====

Add the MeeGo SDK yum repository. Replace ${distribution}/${version} with one of the following: "fedora/12" or "fedora/13".

$ cd /etc/yum.repos.d/
$ sudo wget http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

==== Install the signing key ====

$ sudo rpm --import http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/repodata/repomd.xml.key

==== Update the packages database ====

$ sudo yum update

=== On MeeGo ===

To add the MeeGo SDK repository on a system running MeeGo, run the following command. Replace ${distribution}/${version} with one of the following values: "meego/1.1" or "meego/trunk".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

=== On openSUSE ===

To add the MeeGo repository, run the following command. Replace ${distribution}/${version} with one of the following values: "opensuse/11.2" or "opensuse/11.3".

$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo

== Installing the MeeGo SDK ==
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk</pre>
</li>
</ul>

'''For ARM only:'''
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-armv7l</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-armv7l</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-armv7l</pre>
</li>
</ul>

'''For IA32 only:'''http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-ia32</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-ia32</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-ia32</pre>
</li>
</ul>

== Install MeeGo Target ==
A ''Target'' is used to build programs using the MeeGo toolchain and libraries (sysroot). It is downloaded as a large (~250MB) .bz2 file using the commands below. MADDE (MeeGo Application Develop and Debug Environment ([http://wiki.maemo.org/MADDE background])) is a tool that assists in the download and installation of the Target. "mad-admin" is the MADDE command-line tool. You can install multiple Targets and switch easily between them in Qt Creator (described later).

=== Determine the target you want to use ===

Run the command below. The available targets will be listed under the "Targets:" heading.

$ sudo mad-admin list

Some hints about the target prefixes:

* ''meego-core-armv7l'': Build applications for ARM handheld devices (such as N900)
* ''meego-handset-ia32'': Build applications for x86 handheld devices (such as Aava)
* ''meego-netbook-ia32'': Build applications for x86 netbooks.

=== Create the target ===

Run the command below. Replace <target> with the target you determined in the previous step. Note that the <code>-f</code> flag instructs MADDE to download the Target tarball (bz2) first.

$ sudo mad-admin create -f <target>

If you encounter problems, check the [[MeeGo_SDK_Troubleshooting#General_SDK_Errors|troubleshooting page]].

=== Verify target installation ===

To check that the target has been installed correctly, run the following. Replace <target> with the same value used in the previous step.

$ mad -t <target> pscreate -t qt-simple qthello
$ cd qthello
$ mad -t <target> qmake
$ mad -t <target> make

Note: Running qmake will print "-unix is deprecated". This is not an error with the compilation. You can safely ignore this for now.

=== Verify correct build ===

To check that the qt-simple application is created for the correct target, run the following command, and verify the output.

$ file build/qthello

== Install MeeGo Runtime ==
A ''Runtime'' is the MeeGo OS image that is run with QEMU when debugging applications on your host system. It is not required if you develop against real hardware running MeeGo. It is downloaded as a large (~650MB) .bz2 file using MADDE. The Runtime is not needed until you have finished configuring Qt Creator. However, as this step may take some time, it is recommended to start it now so that it can proceed in the background while you continue following the steps on this page.

See [http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes Downloading a Runtime and Using QEMU]

== Configuring Qt Creator to use the MeeGo toolchain(s) ==

Start Qt Creator by selecting '''Applications''' > '''Programming''' > '''Qt Creator'''.

Configure Qt Creator to use the MeeGo toolchain(s):
# Go to '''Tools''' > '''Options''' > '''Qt4''' > '''Qt Versions'''.
# On the right side of the '''Qt Versions''' view, click on the plus sign button to add a new version.
#: A blank, new version appears in the '''Qt Versions''' view.
# On the '''Version Name''' line, specify a name for the new version.
# On the '''qmake location''' line, specify a qmake location for the new version. The toolchain installs by default to <code>usr/lib/madde/linux-i686/targets/<target>/bin/qmake</code>.
# Click '''Rebuild''', '''Apply''' and '''OK'''.

[[File:Qt Creator adding MeeGo toolchains.png|frame|none|Adding the MeeGo toolchain(s) in Qt Creator]]

=== Using the MeeGo SDK Qt version ===

It is also possible to use Qt Creator without a MeeGo toolchain. This option can be useful if you don't need to cross-compile your software: for example, if you are doing QML development with no use of C++.

The steps are the same as above, but the '''qmake location''' is set to the <code>qmake</code> installed with the meego-sdk-qt libraries. The usual location for this on Linux is:

$ /opt/meego/meego-sdk-qt/bin/qmake

Note: On Ubuntu 10.10, you may need to install g++ in order for this step to work. If necessary, do this:

$ sudo apt-get install g++

== Developing with the SDK ==

To start developing with the MeeGo SDK, the [[SDK/Docs/1.1/Creating_Hello_World|hello world tutorial]] is a good starting point.

This tutorial covers how to start a project, package it, and deploy it to a device (either a real device, or a QEMU runtime set up through MADDE).

== Removing components ==

=== On Ubuntu ===

To remove installed components, run:
$ sudo apt-get remove --purge meego-sdk-qtcreator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu meego-sdk-qt

To remove dependencies related to installed components, run:
$ sudo apt-get autoremove

To remove MADDE directory (it is not automatically removed when "madde" package is uninstalled):
$ sudo rm -rf /usr/lib/madde

To remove the packages from your local repository (<code>/var/cache/apt/archives/</code>), run:
$ sudo apt-get clean

=== On Fedora ===

To remove installed components, run:
$ sudo yum remove meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

=== On openSUSE / MeeGo ===

To remove installed components, run:
$ sudo zypper remove -u meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

== Another language version of this page ==

* [[SDK/Docs/1.1/Memulai_dengan_SDK_MeeGo_untuk_Linux|Memulai dengan SDK Meego untuk Linux - Bahasa Indonesia]]
* [[SDK/Docs/1.1/在Linux平台开发进行MeeGo_SDK开发|在Linux平台进行MeeGo_SDK开发 - 简体中文]]