Hi,

start_over behaves as designed and is easy to control once you understand what
it does. Here is an attempt of explanation.

The start_over script will try to delete all packages installed by OSCAR, thus
listed in the ODA Packages_rpmlists table.

It will also try to delete the packages which depend on the OSCAR RPMs. Not
deleting these would mean to leave these packages unusable (because their
dependencies, the OSCAR RPMs are gone).

And finally it will delete the dependencies of the OSCAR packages, as far as
they are not included in the pre_oscar.rpmlist.

So following packages will be candidates for deletion:
 A: OSCAR packages
 B: packages depending on the OSCAR packages
 C: dependencies of the OSCAR packages

If any of the candidates is leading to the deletion of a package in the
pre_oscar.rpmlist, it will be dropped from the list and left installed on the
system.

A is what we want anyway, B is what we need to delete otherwise B packages
will have unresolved dependencies, C is what we also want to delete, as these
were installed with the OSCAR packages.

If the package you have installed outside of OSCAR and after the OSCAR
installation (thus not appearing on the pre_oscar.rpmlist) is depending on any
of the packages in groups A, B or C, it will be deleted, too. If your package
is not depending on OSCAR packages (or their dependencies), it will be left on
the system.

I think the procedure is understandable and does exactly what we want. And if
you understand how it works, you can control the behavior. I warn everybody
from using the --yes option! The confirmation of the deletion is there for
exactly that purpose: look at the list of packages which will be deleted! If
you find something on it which you don't expect or don't want to be deleted,
type "no" and edit your pre_oscar.rpmlist.

Regards,
Erich



On Thursday 13 July 2006 04:36, Ted Powell wrote:
> On Wed, Jul 12, 2006 at 04:55:54PM -0700, Bernard Li wrote:
> > I don't have time to debug this now, but it appears that the script
> > would uninstall a non-OSCAR package which I have installed while OSCAR
> > was installed.
> 
> Did you remember to add the name of that package to
> $oscar_home/tmp/pre-oscar.rpmlist?
> 
> > Is this a known issue?
> 
> It's an issue I had my nose rubbed in a month ago when start_over fed
> $oscar_home/tmp/pre-oscar.rpmlist to yum without checking first that it
> was non-empty.
> 
> Other people who weren't bitten may be less aware of this list and what
> it is used for.
> 
> 



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to