Re: [android-developers] Re: Eclair install choked with errors about locks and died horribly leaving corrupted install

2009-11-01 Thread Raphael
On Wed, Oct 28, 2009 at 11:25 PM, Armond Avanes armond...@yahoo.com wrote:
 After all, I'm still on my opinion. In the case of failure, the update
 process should try to COPY the contents instead of moving/renaming. And a
 warning that some garbage have been left on temp directory. For those of
 us on slow connections it's really a pain to download that much and throw it
 away!!! I guess I've downloaded 500MB worth of data so far and still
 trying...

The problem with copying is that if a file can't be replaced in the
middle of the copy operation, what do you want the installer to do?
You'd be left with half installed platform mixing some old stuff and
new stuff. Or it'd have to throw away you old install (which might
fail because of a locked folder anyway).

As for the threading issue, I can't figure it out. It's a very
sequential mode of operation right now.

On your last point, you're right, I shouldn't throw away the download
right away if the download was successful yet the install failed. It
would be easy to allow you to retry installing right away.

Still I'd really like to know what can be locking that thing :(

R/

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


RE: [android-developers] Re: Eclair install choked with errors about locks and died horribly leaving corrupted install

2009-11-01 Thread Armond Avanes
Raphael,

The error message says that some files are locked in temp directory not in
destination. At least if you're doing a first-time install (not update), the
destination directory is empty and it's quite safe to copy.

Regards,
Armond

 From: Raphael [mailto:r...@android.com]
 Sent: Monday, November 02, 2009 8:57 AM
 
 On Wed, Oct 28, 2009 at 11:25 PM, Armond Avanes armond...@yahoo.com
 wrote:
  After all, I'm still on my opinion. In the case of failure, the update
  process should try to COPY the contents instead of moving/renaming. And
 a
  warning that some garbage have been left on temp directory. For those
 of
  us on slow connections it's really a pain to download that much and
 throw it
  away!!! I guess I've downloaded 500MB worth of data so far and still
  trying...
 
 The problem with copying is that if a file can't be replaced in the
 middle of the copy operation, what do you want the installer to do?
 You'd be left with half installed platform mixing some old stuff and
 new stuff. Or it'd have to throw away you old install (which might
 fail because of a locked folder anyway).
 
 As for the threading issue, I can't figure it out. It's a very
 sequential mode of operation right now.
 
 On your last point, you're right, I shouldn't throw away the download
 right away if the download was successful yet the install failed. It
 would be easy to allow you to retry installing right away.
 
 Still I'd really like to know what can be locking that thing :(
 
 R/
 
 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en