Line 1: |
Line 1: |
− | This page is an attempt to summarize the problems distributions are having with packaging Sugar activities. Help from the activity maintainers to get them solved would be highly appreciated.
| + | Packaging is the making of a software package for use by a [https://en.wikipedia.org/wiki/Package_manager package manager] in Linux distributions such as Fedora, Debian, or Ubuntu. |
| | | |
− | == Measure == | + | == Common issues == |
| | | |
− | * No source tarball.
| + | === Publish source tarballs for each release === |
− | * Currently hardware specific (?)
| |
| | | |
− | == Maze ==
| + | Some packagers prefer to work from tarballs rather than the activity bundles. This is because activity bundles contain built components instead of only source code. |
| | | |
− | * No source tarball.
| + | ''If your activity is part of Fructose follow [[Development Team/Release#Module_release|Module Release]] instead.'' |
− | * Weird error on Fedora
| |
− | from olpcgames import _cairoimage
| |
− | ImportError: cannot import name _cairoimage
| |
| | | |
− | == Implode ==
| + | * Make a source tarball as follows. It will be placed inside the dist/ directory. |
| + | python setup.py dist_source |
| + | * Upload it on the web. If you need a server to upload it to, [[Service/shell|ask for a shell account]]. When you have access, create a directory under /upload/sources/honey for your activity and copy the tarball to it. |
| + | * Update the Honey table on the [[Development Team/Source_Code#Honey|Source Code]] page with a link to the latest version. Add an entry if your activity is not yet listed. |
| | | |
− | * No source tarball.
| + | === Create a trac component for your activity === |
− | * Shebang/permission mismatch.
| |
| | | |
− | == Distance ==
| + | Users or packagers may report problems with your activity, either; |
| | | |
− | * No source tarball. | + | * enable the Issues feature in the GitHub repository, or; |
− | * Shebang/permission mismatch. | + | * open a ticket on http://bugs.sugarlabs.org, under the trac component, to request a ''component'' for your activity. |
− | * Hardware specific?
| |
| | | |
− | == Bounce == | + | === Check copyright and licensing === |
| | | |
− | * No source tarball. | + | * Many translations lack copyright and licensing info completely or they provide just a boilerplate.The package maintainer should edit the .pot file to replace these: |
− | * C code in the bundle.
| |
| | | |
− | == Etoys ==
| + | SOME DESCRIPTIVE TITLE |
| + | THE PACKAGE'S COPYRIGHT HOLDER |
| + | PACKAGE |
| | | |
− | No known problems.
| + | When that is done, they should get in contact with each translator to |
| + | make them adopt that improved boilerplate and themselves replace these: |
| | | |
− | == Turtle Art ==
| + | FIRST AUTHOR <EMAIL@ADDRESS> |
| + | YEAR |
| | | |
− | No known problems.
| + | When doing above, it makes good sense to also tidy the gettext hints to |
| + | have proper info too, but that is just nice-to-have for semi-automated |
| + | processing, not crucial as the licensing problem. |
| | | |
− | == Terminal ==
| + | [[Category:Activity Team]] |
− | | |
− | No known problems.
| |
− | | |
− | == Jukebox ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Log ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Memorize ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Moon ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Analyze ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Chat ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Calculate ==
| |
− | | |
− | No known problems.
| |
− | | |
− | == Browse ==
| |
− | | |
− | No known problems.
| |