Stephen, > *. I think the overriding question I have is "does every catalog have > an associated update log?" (Every update log has a catalog.) I > believe that the server-side is almost phrased entirely in terms > of the update log, and I'm wondering if we should make that more > clear. Perhaps the update log is derived from the catalog type? > > (Even on the client side, it looks as if the update log is the > changing entity, and the catalogs are just cached state.) > > Perhaps this can be addressed by expanding on the catalog-updatelog > relationship in their docstrings.
Every updatelog must have an associated catalog; however, it's perfectly alright to have a catalog without an update log. As you suggest, I'll update the docs to state this more clearly. If the UpdateLog and Catalog become more tightly coupled, I think it would make sense to have the UpdateLog become a derived class. I'm not sure if we need to do that now, though. Thanks, -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
