We need to have a schema to store plugin meta data. The table would be relatively flat but would have to cover information here: http://svn.mozilla.org/addons/trunk/site/app/webroot/services/pfs.php http://plugindoc.mozdev.org/ In addition, store data to cover: * newest version * update url

Its not clear to me how the schema and scripts would handle multiple product/release families that might be supported for a single plugin. Here is the kind of thing we should design for: Flash might have two supported releases going as they do currently. One in the 10.x family and one in the 9.x family. the checking logic might look something like if user is running 9.x or below make sure they are running 9.0 r152 else upgrade to 9.x r152 if user is running 10.x make sure they are running 10.0 r15 else upgrade to 10.0 r15 at some point adobe will turn off 9.0 support then we would also need to shut that version down. I don't think we can use the minvers/maxversion to reflect this since intermediate versions like 10.0 r12 have security bug vulnerabilities.

Comment on attachment 358431 [details] [diff] [review] v1, patch to add to remora.sql If that stores everything you need, it wfm

Needs to have support for n:1 platforms:plugins relationship.

Going to close this bug in favor of bug 465891, specifically for: https://svn.mozilla.org/projects/pfs2/trunk/conf/schema.sql