On Wed, Jan 14, 2009 at 04:18:08PM -0600, Shawn Walker wrote: > Staged Publishing > ================= > Staged publishing being defined as the ability to publish packages to a > repository without packages from a given publishing "session" being > added to the catalog until explicitly instructed. > > Right now, if clients retrieve a new catalog from a repository as a new > OpenSolaris release is being published, they may inadvertently attempt > to upgrade to a release that hasn't yet had all of its packages > published causing errors.
This makes it sound like we're publishing directly to the servers that people are using as their authorities, which is not the case. If it were, there would be a far better way of preventing the problem -- don't publish entire until the very end, and then no one would be able to upgrade to the new packages sitting on the server (or, once we have the INCOMPLETE state implemented, wouldn't even be able to see them). The problem is more subtle than that, and is probably covered by your "Staged Deployment" section. I'm not sure that "Staged Publishing" solves a real problem. Or am I completely misunderstanding what you're talking about? > Staged Deployment > ================= > Staged deployment being defined as the ability to serve multiple > versions of the catalog. > > This would require changing the depot server to allow the administrator > to provide a date representative of a catalog snapshot > (repo_dir/catalogs/ISO8601DATE/) to serve instead of serving the current > catalog data (repo_dir/catalog/). > > Storing the current catalog in repo_dir/catalog allows backwards > compatibility with our existing depot versions allowing staged > deployment/publishing catalog support to simply be ignored by older > depot versions. We can require a depot upgrade, I think. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
