Bugs item #835459, was opened at 2003-11-03 20:50 Message generated for change (Comment added) made by brechin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=835459&group_id=9368
Category: Installation Group: 2.4 >Status: Closed >Resolution: Fixed Priority: 9 Submitted By: Thomas Naughton (naughtont) Assigned to: John (muglerj) Summary: "missing"/organize install phases Initial Comment: With the new Install/Uninstall some of the existing phases are missed or are not necessarily obvious for order of execution by a user. + The 'setup' scripts seem to be ok, need to be tested. + The Configurator phas (pre_configure, post_configure) is skipped. + The post_install can be run by clicking on Step6 but it's not necessarily obvious that a user should click this after doing the In/Un Execute button. ---------------------------------------------------------------------- >Comment By: Jason Brechin (brechin) Date: 2003-11-20 13:48 Message: Logged In: YES user_id=274641 This seems to be working well enough... ---------------------------------------------------------------------- Comment By: John (muglerj) Date: 2003-11-19 16:45 Message: Logged In: YES user_id=505737 I think this can be closed out. Looks like Terry had a successfull test with the configurator part (see devel list traffic) and all the post_install scripts are being run. ---------------------------------------------------------------------- Comment By: Thomas Naughton (naughtont) Date: 2003-11-15 18:34 Message: Logged In: YES user_id=288102 has this been tested/confirmed? can it be closed? ---------------------------------------------------------------------- Comment By: Terry Fleury (tfleury) Date: 2003-11-13 18:50 Message: Logged In: YES user_id=116599 I modified the install_uninstall_packages subroutine (in PackageInUn.pm) to handle all aspects of Updating installed packages. This subroutine now pops up the Updater (which is simply the Selector run in a different mode). When the Updater finishes, we check to see if any packages were selected for installation. If so, we pop up a dialog asking the user if he wants to run the Configurator. If so, we pop up the Configurator. After that, we do the rest of the steps necessary for installing/uninstalling the selected packages. I am leaving this bug "open" until it can be tested better, but I think the issue with how/when to run the Configurator has been resolved. ---------------------------------------------------------------------- Comment By: Thomas Naughton (naughtont) Date: 2003-11-12 15:08 Message: Logged In: YES user_id=288102 What's the status of the Configurator aspect? Does it now automatically process the Configurator if needed or does it require the user to manually click it? ---------------------------------------------------------------------- Comment By: Thomas Naughton (naughtont) Date: 2003-11-11 09:04 Message: Logged In: YES user_id=288102 Can this be closed? ---------------------------------------------------------------------- Comment By: Jason Brechin (brechin) Date: 2003-11-05 09:18 Message: Logged In: YES user_id=274641 Actually, all the post_install scripts should be run. What about packages that are checking to see what other packages are installed and doing something accordingly? I don't know if this is done by any package right now, but it is a reasonable situation that would require all (installed packages') post_install scripts to be run. ---------------------------------------------------------------------- Comment By: Thomas Naughton (naughtont) Date: 2003-11-05 07:05 Message: Logged In: YES user_id=288102 Cool, and I believe John checked in his update that ran 'post_install' for the given packages so that should take care of the 3rd item. ---------------------------------------------------------------------- Comment By: Terry Fleury (tfleury) Date: 2003-11-04 20:18 Message: Logged In: YES user_id=116599 I fixed the 2nd problem of the Configurator phase. The Configurator now looks at selected packages in the current package set (which it used to do) AND packages which "should_be_installed" (as set by the Install/Uninstall Package phase). This isn't a perfect fix since the user can configure packages which may have already been installed (and thus nothing will happen for that package), but it's a hack which should be good enough for SC'03. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=835459&group_id=9368 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
