Hi Liane,
Thank you for this write-up as it makes the future far less foggy.
I do have a question though, as for install, we usually build on a release
or two behind OS\Net:
On Wed, 28 Oct 2009, Liane Praza wrote:
[snip...]
- Consolidations will produce repositories which have
dependencies specified using pkgdep. Dependencies between
packages in the same consolidation will be specified at the
current version of the consolidation. Dependencies on system
components from outside the consolidation will be specified on
the version of the component installed at build time.
[snip...]
So, if I understand the last sentence correctly, I would need to run on
build 127 to build the Install packages for build 127?
If so, this seems problematic for a gate who's components are tied
to each OpenSolaris build but isn't necessarily built on that version of
OpenSolaris. We could change our development process to be tracking the
nearly nightly ON packages but that would bring more risk (of catching a
bug which brings our build servers down, for example) than we've
traditionally accepted. Is there any envisioned path for this scenario?
(Certainly, the Install components not being in ON is a bug working to be
rectified). I think only Install, IPS and JDS are in this boat?
Thank you,
Clay
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
