Hi Brock, > One problem this is trying to solve is the situation where one (or more) > of your authorities is offline, but not actually needed for the > install/update that's being attempted. For example, the packages ares > coming from repo Y, but you also have repo Z as an authority, but Z is > down. It would be nice if image-update proceeded (which it doesn't > today) and if install did not try to refresh the catalog from Z and then > die.
I hadn't considered this case, although I suppose it might be covered by a don't-bother-to-refresh-flag. What do you do in the case where the user requests package A that is installed from repo 1, but it depends upon package Q that is installed from repo 7? Are you going to perform a second refresh after dependency evaluation? It seems like it would be possible to be arbitrarily complicated with our evaluation, if we so desired. It might be simpler to just refresh as many catalogs as possible the first time around. > I'm not sure what the advantage of the N minutes approach is other than > its simplicity. Do you think the above approach is wrong, or just > needlessly complex? I don't think your approach is wrong, but it may need further refinement. If we have dependencies that cross authority boundaries, the algorithm below may not refresh all the catalogs that need to be refreshed. I'm also concerned that we might end up doing more work than we need to, just to come to a relatively simple conclusion. > >> For pkg install: > >> 1) If a fmri with the version including the timestamp is given, no > >> catalog refresh will be done. > >> > >> 2) Else: If the fmri specifies an authority or the package was > >> previously installed from a specific authority, then that authority's > >> catalog will be refreshed, but no others will. If that authority is > >> unavailable, installation will fail. > >> > >> 3) Else: The catalogs for the preferred authority and the authority the > >> package was previously installed from will be refreshed. If neither > >> authority is available, the install will fail. If at least one of the > >> authorities is available, then installation will proceed. 4) In the case where the package has never been installed before, and no authority is specified in the FMRI, do we just refresh the preferred authority? -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
