<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://maemo.octonezd.me/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=78.148.148.32</id>
	<title>Maemo Wiki Mirror - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://maemo.octonezd.me/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=78.148.148.32"/>
	<link rel="alternate" type="text/html" href="https://maemo.octonezd.me/index.php/Special:Contributions/78.148.148.32"/>
	<updated>2026-04-22T01:45:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://maemo.octonezd.me/index.php?title=Extras-devel&amp;diff=9742</id>
		<title>Extras-devel</title>
		<link rel="alternate" type="text/html" href="https://maemo.octonezd.me/index.php?title=Extras-devel&amp;diff=9742"/>
		<updated>2012-07-26T01:40:45Z</updated>

		<summary type="html">&lt;p&gt;78.148.148.32: /* Limiting the damage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ambox&lt;br /&gt;
| type = notice&lt;br /&gt;
| image= &lt;br /&gt;
| text = &#039;&#039;&#039;The software hosted in [[extras-devel]] is not ready for normal users!&#039;&#039;&#039;&amp;lt;br /&amp;gt;&amp;lt;small&amp;gt;PLEASE PLEASE PLEASE don&#039;t play with it unless you really know what you are doing. Be ready to [http://maemo.org/development/bugs/ file proper bug reports] instead of posting complaints.&lt;br /&gt;
&#039;&#039;&#039;Expected problems&#039;&#039;&#039;: crashes, battery drain, poor system performance, full disk space &amp;amp; more - SERIOUSLY!&lt;br /&gt;
Don&#039;t play with Extras-devel if you haven&#039;t &#039;&#039;&#039;backed up your data&#039;&#039;&#039; or aren&#039;t prepared to [[Updating the firmware|re-flash your device]].&amp;lt;/small&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Developers upload the newest version of their software to extras-devel. From there the packages go [[Extras-testing]] and finally [[Extras]] through an automatic and human Quality Assurance process. This is a repository for developers and regular contributors of specific software projects. If you want to play with extras-devel software you need to be prepared to feel some pain sooner or later.&lt;br /&gt;
&lt;br /&gt;
== For developers ==&lt;br /&gt;
=== Uploading to Extras-devel ===&lt;br /&gt;
{{main|Uploading to Extras-devel}}&lt;br /&gt;
Anyone with a [http://garage.maemo.org/ Garage] account can upload packages to Extras-devel in order to share new updates and start the community QA process. It is important to note that the &#039;&#039;uploader&#039;&#039; needs a Garage account: the package itself does not need to be hosted in the Garage.&lt;br /&gt;
&lt;br /&gt;
==== Promoting packages to extras-testing ====&lt;br /&gt;
&lt;br /&gt;
Developers can tinker as much as they want in the extras-devel repository. Once they think their application is ready to go public they need to promote it to extras-testing by following these steps:&lt;br /&gt;
&lt;br /&gt;
1. Go to the armel version of your application in the [http://maemo.org/packages/ maemo.org packages interface].&lt;br /&gt;
* This will be at maemo.org &amp;gt; packages &amp;gt; Fremantle Extras-devel free armel &amp;gt; &#039;&#039;packagename&#039;&#039; &amp;gt; &#039;&#039;version&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
2. Check if you are listed as maintainer for the package.&lt;br /&gt;
* This should correspond to your login name - you must be logged in&lt;br /&gt;
&lt;br /&gt;
3. Check if there is a &#039;Promote package&#039; link, if there is: click it&lt;br /&gt;
* This is normally in the lower-right corner of the package description&lt;br /&gt;
&lt;br /&gt;
If there are no errors shown your application will be promoted to extras-testing. This can take some time.&lt;br /&gt;
&lt;br /&gt;
In case there are warning or errors on the details page of your package, please try to resolve these issues first. If the interface doesn&#039;t detect any problem, it will unlock the &#039;Promote package&#039; link automatically.&lt;br /&gt;
&lt;br /&gt;
You don&#039;t have to promote the i386 versions of your packages, they will be promoted automatically.&lt;br /&gt;
&lt;br /&gt;
A promotion can fail because your application depends on an other &#039;user/*&#039; category application. In this case you need to promote the other application first and wait until that package shows up in Extras-testing.&lt;br /&gt;
&lt;br /&gt;
==== Promotion checks ====&lt;br /&gt;
&lt;br /&gt;
The package interface will try to prevent promotion for packages with known issues. The following tests are in place:&lt;br /&gt;
&lt;br /&gt;
* Application is using one of the official &#039;user/*&#039; sections.&lt;br /&gt;
* Promoting person is maintainer for the package.&lt;br /&gt;
* All specified dependencies can be found in the origin repository or neighbour repositories.&lt;br /&gt;
* All specified version dependencies are met.&lt;br /&gt;
* Application doesn&#039;t depend on another &#039;user/*&#039; application which hasn&#039;t been promoted yet.&lt;br /&gt;
* Check if all dependencies which are in origin and not in target can be promoted.&lt;br /&gt;
* Check dependencies of dependencies. (Check complete tree)&lt;br /&gt;
* Check if the application hasn&#039;t been promoted already&lt;br /&gt;
&lt;br /&gt;
==== Maemian/Minimae checks after builds ====&lt;br /&gt;
&lt;br /&gt;
Jeremiah implemented the following checks in minimae for the October Sprint:&lt;br /&gt;
&lt;br /&gt;
* Control information is UTF-8&lt;br /&gt;
* Control file contains an image (Not having an image is not an error, it&#039;s just that minimae should notice if there is an image or not, its size and type. This check is only done for user/ apps since libs have no icon.)&lt;br /&gt;
* XB- (or XS-) Fields in control file&lt;br /&gt;
* Version is consistent with what is in changelog&lt;br /&gt;
* Use of trademarked names in package (not in version string.) i.e. A package cannot be called MaemoCamera or MaemoMusic since that is use of a registered trademark.&lt;br /&gt;
* Make sure the name of the binary package that gets built is the same as the package name. i.e. a package called foo should build a binary called foo, not bar.&lt;br /&gt;
* Each package has to have a copyright file&lt;br /&gt;
* Copyright file cannot be compressed, i.e. zipped&lt;br /&gt;
* Remove helper files from copyright, check for properly assigned copyright&lt;br /&gt;
* Make sure the Architecture field is correct according to debian specifications. I.e. all, any, or a specific arch - multiple arches not allowed.&lt;br /&gt;
&lt;br /&gt;
=== Policy ===&lt;br /&gt;
{{main|Task:Consolidation of Extras}}&lt;br /&gt;
The Extras policies are still in the process of being defined and refined. See [[Extras repository process definition]] and [[Diablo Extras repository proposal]] for details and discussion.&lt;br /&gt;
&lt;br /&gt;
See also the [[Extras/3rd Party Package Policy]] being tested in Fremantle.&lt;br /&gt;
&lt;br /&gt;
=== Downloads OBSOLETE FIXME===&lt;br /&gt;
{{main|Task:Providing changes since last version of a package}}&lt;br /&gt;
You can [https://maemo.org/downloads/product/create/OS2008/application.html create an entry] for your application in the [http://maemo.org/downloads maemo.org downloads section]. If the unixname of your entry is the same as your debian package in Extras, the version information will be automatically updated when you upload a new package.&lt;br /&gt;
&lt;br /&gt;
There is a discussion going on about how to provide changes since last version of a package. At the moment there isn&#039;t a conclusion to this discussion yet.&lt;br /&gt;
&lt;br /&gt;
=== How to activate Extras-devel ===&lt;br /&gt;
&lt;br /&gt;
In the Application Manager:&lt;br /&gt;
&lt;br /&gt;
# Navigate to the application menu (tap the title bar)&lt;br /&gt;
# Select ‘Application catalogs’&lt;br /&gt;
# Select ‘New’&lt;br /&gt;
# Enter a catalog name of ‘Maemo extras-devel’&lt;br /&gt;
# Enter a web address of http://repository.maemo.org/extras-devel/&lt;br /&gt;
# Enter a distribution of ‘fremantle’&lt;br /&gt;
# Enter components of ‘free non-free’&lt;br /&gt;
# Select ‘Save’&lt;br /&gt;
&lt;br /&gt;
=== Limiting the damage ===&lt;br /&gt;
To keep from unintentionally upgrading to an extras-testing or extras-devel software version, it is possible to tell apt to always prefer stable packages over these other repositories via apt-pinning. &lt;br /&gt;
&lt;br /&gt;
Note: If you use Faster Application Manager, then the following will cause errors, so don&#039;t do it and just be careful with what repos you enable.&lt;br /&gt;
&lt;br /&gt;
Create the file /etc/apt/preferences with the following content:&lt;br /&gt;
 Package: *&lt;br /&gt;
 Pin: release l=Extras&lt;br /&gt;
 Pin-Priority: 1001&lt;br /&gt;
&lt;br /&gt;
Then run&lt;br /&gt;
 rm /var/cache/apt/*.bin&lt;br /&gt;
 apt-get update&lt;br /&gt;
&lt;br /&gt;
In order to install versions of software from extras-testing or extras-devel when there is a copy available in extras, you now must tell apt exactly what version of software to install.  Run &lt;br /&gt;
 apt-cache showpkg &amp;lt;package&amp;gt;&lt;br /&gt;
&lt;br /&gt;
At the bottom there will be a listing of versions under &amp;quot;Provides:&amp;quot; .  To install a particular version use &lt;br /&gt;
 apt-get install &amp;lt;package&amp;gt;=&amp;lt;version&amp;gt;&lt;br /&gt;
In the application manager, if you look in install/details/summary, there is a line &amp;quot;Catalog.&amp;quot;  Applications being installed from extras have the catalog &amp;quot;maemo.org&amp;quot;, applications from extras-testing have &amp;quot;Maemo extras testing&amp;quot;, and applications from devel have &amp;quot;devel&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>78.148.148.32</name></author>
	</entry>
</feed>