<br><br><div><span class="gmail_quote">On 8/13/07, <b class="gmail_sendername">Neil MacLeod</b> <<a href="mailto:gmane@nmacleod.com">gmane@nmacleod.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Marius Vollmer wrote:<br>> "ext Neil MacLeod" <<a href="mailto:gmane@nmacleod.com">gmane@nmacleod.com</a>> writes:<br>><br>>> Perhaps if someone can identify the method currently being used by<br>
>> the Application Manager to group applications it can cut down on the<br>>> guesswork, and give us a base from which to move forward.<br>><br>> <a href="http://hildon-app-mgr.garage.maemo.org/packaging.html">
http://hildon-app-mgr.garage.maemo.org/packaging.html</a><br><br>Thanks.... and I give up. The predefined sections in the packaging guide matches quite closely the list of "categories" I had proposed in this mailing list.
<br><br>What is missing is a vetting procedure to avoid the chaos we currently have.<br><br></blockquote></div>Perhaps the application manager could require one of those categories is used or it shows up "Not Installable" just as occurs when the package is not in the user category?
<br><br>It would be a real pain when it first happens, but if the majority of developers were notified via the list and with a note(s) on <a href="http://maemo.org">maemo.org</a>, etc, programs could be repackaged before the update when that's applied. Since nobody will want their users to require red pill mode to install, they'll fit it into one of the "acceptable" categories that most closely fits.
<br><br>--Paul<br>