On Thu, Jun 21, 2012 at 5:55 PM, Anthony Lenton
<email address hidden> wrote:
> If there is data in MyApps for an app, import_app_install_data should
> not update this, as we assume MyApps will have more up-to-date
> information.
>
> Neither commands should create another instance for the same
> package_name and distroseries if one already exists.
Yep, makes sense.
>
> import_app_install_data could check if the app has a non-null
> "Application id" field, and keep its hands off the app entirely if so.
For bug 1015505 I'll be renaming Application.for_purchase to
Application.imported_from_sca which will enable us to know when to
overwrite and when not. I'll fix this at the same time.
On Thu, Jun 21, 2012 at 5:55 PM, Anthony Lenton app_install_ data should
<email address hidden> wrote:
> If there is data in MyApps for an app, import_
> not update this, as we assume MyApps will have more up-to-date
> information.
>
> Neither commands should create another instance for the same
> package_name and distroseries if one already exists.
Yep, makes sense.
> app_install_ data could check if the app has a non-null
> import_
> "Application id" field, and keep its hands off the app entirely if so.
For bug 1015505 I'll be renaming Application. for_purchase to imported_ from_sca which will enable us to know when to
Application.
overwrite and when not. I'll fix this at the same time.