public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Will <will@phase.net>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org
Date: Tue, 9 Jul 2013 13:13:16 +0200	[thread overview]
Message-ID: <CAHQs=o5cZCNaiDmH=h3XqxxigWeXbkDMLBr0fSCxTiJtCOJUAA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3zi4sWBJa-9hu4S2+gT5pP-6JzNi=mJQi=OnzF5iZE_w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

Omaha - which is the automatic update framework that Google Chrome uses -
is open sourced:

https://code.google.com/p/omaha/

It might be a bit heavyweight for just one package though.

Will

On 9 July 2013 13:04, Mike Hearn <mike@plan99.net> wrote:

> For the auto update, is there an existing auto update framework that we
> can modify to support threshold signed updates? I'm sure such a thing must
> exist. The updates would download in the background and then the app can
> just ask the user to restart it once the update is locally available, as
> Chrome does.
>

[-- Attachment #2: Type: text/html, Size: 1086 bytes --]

  reply	other threads:[~2013-07-09 11:35 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 17:10 [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org Jim
2013-06-27 17:30 ` Jeff Garzik
2013-06-27 18:04   ` Luke-Jr
2013-06-27 18:41     ` Gregory Maxwell
2013-06-27 19:18       ` Jim
2013-06-27 19:40         ` Jim
2013-06-27 19:50           ` Jim
2013-06-27 21:12         ` Alex Kravets
2013-06-27 21:56           ` Jeff Garzik
2013-06-27 22:53             ` Alex Kravets
2013-06-27 22:03           ` Gary Rowe
2013-06-28 10:59       ` John Dillon
2013-06-28  9:10   ` Mike Hearn
2013-06-28 14:24     ` Gavin Andresen
     [not found]       ` <CAFtwHRewE0wgvWsf-785hpCb8ns7wiGaKHAQ-1QmDD-W+diBJA@mail.gmail.com>
2013-06-28 20:37         ` Bill Hees
2013-06-28 20:42           ` Jim
2013-06-30 11:42       ` Mike Hearn
2013-06-30 15:19         ` Jim
2013-06-30 16:39           ` Gary Rowe
2013-07-09  0:22             ` Robert Backhaus
2013-07-09  1:20               ` Caleb James DeLisle
2013-07-09 10:36                 ` Mike Hearn
2013-07-09 10:56                   ` Jim
2013-07-09 11:04                     ` Mike Hearn
2013-07-09 11:13                       ` Will [this message]
2013-07-09 11:15                       ` Jim
2013-07-09 11:18                       ` Mike Hearn
2013-07-09 14:00                     ` Daniel F
2013-07-09 14:06                       ` Jeff Garzik
2013-07-09 14:28                         ` Mike Hearn
2013-07-09 14:46                           ` Jim
2013-07-09 14:57                           ` Daniel F
2013-07-09 15:27                             ` Mike Hearn
2013-07-09 15:32                               ` Nick Simpson
2013-07-09 15:51                                 ` Johnathan Corgan
2013-07-09 16:44                                   ` Mike Hearn
2013-07-09 15:59                                 ` Jeff Garzik
2013-07-09 16:03                                   ` Nick Simpson
2013-07-09 22:15                                   ` Andreas Petersson
2013-06-27 17:56 ` Gregory Maxwell
2013-06-27 18:05   ` Alex Kravets
2013-06-27 23:45   ` Caleb James DeLisle
2013-06-28  9:05   ` Mike Hearn
2013-06-28 10:09     ` John Dillon
2013-06-28 10:20       ` Mike Hearn
2013-06-28 10:32         ` John Dillon
2013-06-30 10:12       ` Peter Todd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHQs=o5cZCNaiDmH=h3XqxxigWeXbkDMLBr0fSCxTiJtCOJUAA@mail.gmail.com' \
    --to=will@phase.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mike@plan99.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox