* Leslie H Wood <Leslie.Wood at Sun.COM> [2009-02-18 19:28]: > Stephen Hahn wrote, On 02/18/09 11:38: > > * Leslie H Wood <Leslie.Wood at sun.com> [2009-02-18 18:21]: > > > So if I read this correctly, the only way we can control what package > versions are used for both the OS and add on packages is through > maintaining separate repositories ? > > Since Sun Mfg installs have a mix and match requirement for add on packages > we have a modular approach that installs the required OS version and then > the additional packages, netbeans, SSexp, LDOM etc as needed usually by a > part number. > > I have been searching opensolaris.org for clues on how to do this... > > > Use the entire package, at some specific version, to constrain the > > installation to a particular build or release. > > Can you expand on the above since I have found that "pkg install" only > uses the VALUE section > > root at g-unit6:/var/tmp# pkg search -r netbeans > > INDEX ACTION VALUE PACKAGE > > description set NetBeans pkg:/SUNWlibnb-apisupport1 > at 6.1-0.86 > > description set NetBeans pkg:/SUNWlibnb-apisupport1 > at 6.0.1-0.86 > > description set NetBeans pkg:/SUNWlibnb-apisupport1 > at 6.0.1-0.86 > > description set NetBeans pkg:/SUNWlibnb-apisupport1 > at 6.0.1-0.86
We will need to provide incorporations for the netbeans package, so that they get self-consistent sets of the component packages. Those are not there at present. > (This procedure will change in the future, but works at present.) > > We need a long term solution though... Any RT.M pointers also > appreciated. The aspect that would change is that we're pretty likely to blow up entire (into smaller pieces to support minimization). - Stephen -- sch at sun.com http://blogs.sun.com/sch/
