Joe Higgins wrote: > I see one caveat in the man page about > > Please note that updating > specific packages across package rename or obsolete boundaries > is not supported. > > > So are they any additional scenarios WRT to downgrading packages which > customers need to be concerned about.
When you downgrade a package, packages that depend on it might also need to be downgraded, and that dependency chain may cascade pretty far, depending on how core a package it is that you're trying to downgrade. I hope at some point we'll be able to build most of our leaf packages on old versions of the core, but most of our build systems can't yet handle that effectively. But that's just another form of not being able to move a particular package from one version to another because of constraints other installed packages are placing on it, such as incorporations that prevent you from moving forward, and so on. The problems with rename and obsolete are different. First is that in the case of obsolete (and rename, if nothing on the system still depends on the old name), the package is simply removed, so there's really nothing to update backwards from -- it's essentially just an install. You can usually install a non-obsolete version of a now-obsolete package (modulo other constraints). If you downgrade a renamed package, you can also run into the issue that the older version and the newer (renamed) version share the same files, so both can't be installed at the same time. We'll tell you that there are conflicting actions, but we don't analyze the case to tell you that it's a downgrade-across-rename, nor do we auto-remove the new name. Danek _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
