Danek Duvall wrote: > On Wed, Nov 28, 2007 at 08:01:01PM -0800, Chris Quenelle wrote: > >> My plan for dependencies was to create a meta-package of some >> kind by hand that listed the specific versions of all 100ish >> packages we have. So essentially the early releases would >> be an all-or-nothing sort of thing, just like we have today. >> >> Does that approach let us get away without adding extra >> explicit dependencies? It seems like it should. > > As long as you're quite clear that the only supported thing to do is to > install and upgrade that top-level package, and that currently the only > upgrade option is to upgrade to latest, then yes, it'll do for now.
Users should also be able to downgrade to a complete set of older packages right? Or install two different sets on the same machine in different images. That basically reproduces what you get with a plain tarball, only integrated with other bits in a common depot. That's what I'm shooting for in phase 1. > > We need incorporations in order to be able to really do the right thing > with the cluster-like package; that's something Stephen's working on. And > ultimately, you should be able to upgrade a single package inside the > cluster and be confident that that upgrade upgraded other packages it > needed as well, but you'd need true dependencies for that. > > And, of course, you won't have dependencies on the core packages, so you'd > be able to install without having, say, SUNWcsl on the system, which > probably won't work too well. ;) But we can probably assume, for now, > that people aren't going to do that. :) There are some dependencies that our current Sun Studio installer checks for. I can probably add some of those by hand. I'll have to dig them out of our installer code. --chris _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
