[maemo-developers] Application manager category view proposals
From: Ryan Abel rabelg5 at gmail.comDate: Tue Oct 28 13:33:18 EET 2008
- Previous message: Application manager category view proposals
- Next message: Application manager category view proposals
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Oct 27, 2008, at 10:47 AM, Marius Vollmer wrote: > "ext Andrew Flegg" <andrew at bleb.org> writes: > >> On Mon, Oct 27, 2008 at 1:47 PM, Marius Vollmer >> <marius.vollmer at nokia.com> wrote: >>> >> [snip: packages with sections which aren't "liked"] >>> >>> You don't need to reject the packages: you can also rewrite rogue >>> sections to "Other". >> >> There has, previously, been very strong (and probably justified) >> revulsion at the idea of the autobuilder changing the uploaded >> packages. > > You can put overrides into the archive: only the "Packages" files in > the > repository would be affected, the packages themselves can remain > untouched. The reason I like doing this Application Manager-side is that it forces compliance even for stuff not going through the autobuilder or Extras. This prevents both Nokia and 3rd party repositories from being evil and corrupting the category view. apt pulls in a lot of data from the repositories when it does an update anyway, so why not pull in the authoritative list (including section names, encoded icons, i18n and anything else that's relevant) from repository.maemo.org during these updates? Enforcement is done in the Application Manager but doesn't require the Application Manager to be updated to update the section list. -- Ryan Abel Maemo Community Council chair
- Previous message: Application manager category view proposals
- Next message: Application manager category view proposals
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]