Great, this solution is what I was looking for. Collin
On Tue, Nov 24, 2009 at 1:21 PM, Erik Kay <erik...@google.com> wrote: > Hi Collin, > This is definitely something we've considered, but it won't be directly > supported in the initial version of the gallery. The underlying autoupdate > system does in fact support the concept of multiple update channels (it's > the same functionality that Chrome uses as well), so we have the ability to > do this automatically on your behalf, without requiring multiple ids. > The issue for implementation was primarily a question of how to expose this > in the UI. There was also the question of how many developers would really > be interested in using a feature like this. Given the combination of these > factors, it didn't make the cut for our initial release. I don't think we > have an external bug filed against this yet, so feel free to file a new one > if you think this would be useful to you. > That said, I think what you're proposing could work as a workaround until we > have this as a fully supported feature. Here's what you would do: > (1) package your extension on your own and save your key > (2) make a copy of your extension and remove the autoupdate URL from your > manifest > (3) upload your zip file with your key inside named "key.pem" > Now you've got two versions of the same extension id, each with different > autoupdate URLs. If you wanted the one you hosted to be your beta version, > just keep its version numbers ahead of the gallery version. In this way, if > the user tried to install the gallery version over the beta, it would fail > because it was an older version. However, if they installed the beta over > stable, it would over install and upgrade the user to the beta version. > Obviously, in this world, you'd need to host the beta version updates > yourself. > Erik > > On Tue, Nov 24, 2009 at 12:55 PM, Collin Jackson <col...@cooliris.com> > wrote: >> >> Is it possible to host "beta" versions of an extension from the >> extension developer's web site, and have a "stable" version with the >> same id hosted in the official gallery, so that they both autoupdate >> to the same extension when a new stable version is released? Perhaps >> the gallery could provide a way for developers to sign an extension >> using their gallery .pem without actually replacing the latest gallery >> version of their extension. If there's no way to do this with a single >> id, is there a way that the stable version of the extension can detect >> that a beta version of the extension (with a different id) is also >> present and refuse to install itself (to avoid the double install >> problem)? >> >> On Tue, Nov 24, 2009 at 4:10 AM, Lex1 <ruza...@gmail.com> wrote: >> > New pem -> new id -> problems with double installing for 100K users. >> > Bad idea. >> > >> > -- >> > >> > You received this message because you are subscribed to the Google >> > Groups "Chromium-extensions" group. >> > To post to this group, send email to >> > chromium-extensi...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > chromium-extensions+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/chromium-extensions?hl=en. >> > >> > >> > >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Chromium-extensions" group. >> To post to this group, send email to chromium-extensi...@googlegroups.com. >> To unsubscribe from this group, send email to >> chromium-extensions+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/chromium-extensions?hl=en. >> >> > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
