[ros-bugs] [Bug 4934] rapps can't install any app (hangs)

[ReactOS.Bugzilla at reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=4934





--- Comment #26 from LoveN <love.nystrom at gmail.com>  2009-11-07 14:59:25 CET ---
(In reply to comment #25)
> But if installers are hanging on ROS that were not hanging before and/or do not > hang on windows, an appropriate fix needs to be done.

  That is very true.. But that doesn't preclude fixing issues in rapps.
  Just because Your car has a flat tire doesn't imply You
  should neglect fixing the flat tire on Your bicycle.. Right?

> And RAPPS may need to be reworked as GED suggested, IMO.

  I exchanged words with Ged and his idea was identical to
  my original idea.. To let rapps "fire and forget" so to speak.

  *Incidentally this patch facilitates exactly that*.
  It merely begins by waiting a while to see if the installer will finish.
  Then it asks politely if it should wait longer.
  When the user responds No, rapps moves on and lets the installer
  continue without rapps watching over it.

  If the user is a member of Admin, he's given an additional option 
  to attempt a kill on the installer (it is assumed Admin is no idiot).
  If he says No, rapps just goes on it's merry way.

  Whether this code is included in ROS or not, I will probably continue
  to use it myself, in my own customized ROS tweak.
  Initially my impression was that rapps was a bit tangled,
  but my impression has started to change.

  I have discovered additional issues in Rapps and are beginning to
  look into it, but I cannot assign all my time to it, so it will
  not give results immediately. I shall contact Dimitry (it's his code
  if I recall it right), and see what he thinks. Maybe we can join forces..

  Best Regards // Love


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.