maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Making a package for the Application Manager in maemo 3.x does not list what apps should go to what section|
|Product:||[Documentation] Developer Guide||Reporter:||Jarmo Tikka <jarmo.tikka>|
|Component:||maemo.org wiki||Assignee:||Niels Breet <maemo>|
|Status:||RESOLVED FIXED||QA Contact:||documentation <documentation>|
|Priority:||Medium||CC:||andre_klapper, eero.tamminen, ferenc, quim.gil, rabelg5|
|Bug Depends on:||3845|
Problem discussed in maemo mailing list in maemo packaging documentation. This is what maemo documentation has to say about sections: **** (http://maemo.org/development/documentation/how-tos/3-x/howto_making_an_application_package_bora.html) The list of predefined subsections and their English names is: * user/accessories Accessories * user/communication Communication * user/games Games * user/multimedia Multimedia * user/office Office * user/other Other * user/programming Programming * user/support Support * user/themes Themes * user/tools Tools **** It defines the software sections, but it doesn't tell what applications is supposed to go to what section. This should be explained. Note 1, Sections should match maemo application catalog categories. Catalog user manual (http://maemo.org/community/application-catalog/user-manual) should be updated to refer updated sections policy when available. Note 2, Sections used in Debian are listed here (for example) http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections. To avoid unnecessary patching of packages maemo sections should match as much as possible debian ones.
Added Eero Tamminen to the report.
Just a comment that instead of sections tags sho0uld be used to categorize packages. See http://debtags.alioth.debian.org/
Ah, adding URLs without any further comments. Great. So has this been improved for 4.1?
Conveniently updated, this belongs to "Better extras categories and debtags", a task committed for Sprint2.
This bug seems to be in process already. Just added Marius Vollmer as CC.
Moving Documentation component from maemo.org to Development Platform since the bugs there refer to official developer documentation and this falls out of the responsibility of the community. Sorry for the noise, you can filter your bugmail by searching for this comment.
This does not look like high prio to me if that was set 4 months ago. Correcting.
We are updating Diablo release docs but because there has not been "official" update for this to maemo packaking policy http://maemo.org/forrest-images/pdf/maemo-policy.pdf but just discussion and proposal in maemo wiki http://wiki.maemo.org/Task:Packaging_policy_proposed_changes we will not fix this to Diablo documentation. Bug target milestone changed for Fremantle.
(In reply to comment #9) > We are updating Diablo release docs but because there has not been "official" > update for this to maemo packaking policy > http://maemo.org/forrest-images/pdf/maemo-policy.pdf but just discussion and > proposal in maemo wiki > http://wiki.maemo.org/Task:Packaging_policy_proposed_changes we will not fix > this to Diablo documentation. > > Bug target milestone changed for Fremantle. > Well, the policy is blocked until the Application Manager is updated ('policy follows tools'), but that list of categories is finalized for Diablo.
(In reply to comment #10) > (In reply to comment #9) > > Bug target milestone changed for Fremantle. > > Well, the policy is blocked until the Application Manager is updated ('policy > follows tools'), but that list of categories is finalized for Diablo. So this could be done now I guess.
This seems to be FIXED in Fremantle?
Resolving as Fixed in Fremantle.
[Rearrangement of Documentation bug reports.] Mass-moving old closed Developer Platform > Documentation tickets. You can filter bugmail by searching for this comment.