On Fri, Oct 30, 2009 at 05:03:39AM -0700, Liane Praza wrote: > Venky wrote: >> On Fri, Oct 30, 2009 at 11:12:36AM +1300, Laszlo (Laca) Peter wrote: >>> On Thu, 2009-10-29 at 07:57 -0700, Liane Praza wrote: >>> >>>>> In Desktop, we are planning to rebuild only what's changed, >>>>> and what needs to be rebuilt as a result of a change in another >>>>> component. Would we publish an incorporation that includes >>>>> package versions from different "builds"? >>>> How is testing done to ensure that, say, new pidgin works with old >>>> libdbus-glib? It's the collection that developers and test orgs >>>> validate that should be incorporated. If you're testing the mix of >>>> packages, then that's indeed what should be incorporated. >>> Okay, understood. The incorporation will include the versions >>> that we build and test against. >> >> Hmm.. I get this. But in Liane's example above, wouldn't the >> version of libdbus-glib pidgin is built with be recorded as >> a dependency? Would we need an incorporation to make sure >> libdbus-glib is upgraded along with pidgin? > > Dependencies specify at-least-this-version. So, you're right that > libdbus-glib would get upgraded due to the dependency. But... > > Incorporations specify exactly-this-version. From a support/test > perspective, there may be no guarantees that the /next/ version of > libdbus-glib will work with pidgin (especially if they were an example > from a consolidation that had lots of private and rapidly evolving > interfaces between them). So an incorporation constrains the system to a > known-working (through testing) set of software.
Right, got it. Essentially, in this case, it makes sure we don't end up with a newer libdbus-glib than the one pidgin was tested with. Thanks, Venky. _______________________________________________ pkg-discuss mailing list pkg-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
