Sean McGrath wrote: > The suituation: > Network boot a machine with AI image osol_0906-106a > Fine, creates the zpool, pulls the pkgs from repo, sets up grub etc.. > All nice. > > However the latest bits on the IPS repo are snv_107 based. > > So all the pkgs pulled with this 106 based AI image are snv_107 ones. > So we end up with a snv_107 based osol installed machine. > > The package version can be specified in the manifest like: > <ai_packages> > <package_name>slim_install at 0.1,5.11-0.106</package_name> > </ai_packages> > > (right ?) > > but on an AI server which may be installed a few dozen machines at > any given time and where scripts to create manifests can break :}, > theres an amount of work needed to be sure we install with what we want. > We may want to at any time install AI image $bar and not have version $foo > installed. > > As an enhancement, the AI image could pull packages whose version > matches its own build. Eg. for osol_0906-106a it'd pull version > 0.5.11,5.11-0.106 packages unless otherwise specified in a manifest. > > Without this enhancement, the suituation could arise where an older > version of an AI image is used, it creates a zpool, installs the pkgs etc. > However on rebooting the machine finds its zpool being an older version, > the grub menu possibly different to what it expects, even perhaps the > boot_archive synced with the AI image's idea of the universe instead of > the version on disk. > > Sound viable ? > > Logged this as an RFE: > 6724 AI image should perhaps specifiy the pkg versions of any pkgs it > pulls from a repo >
No, in my opinion that's an undesirable skew from the default behavior that users will get with running "pkg" directly and will lead to even greater confusion in that direction. If you want a specific branch, you need to specify that branch in the manifest, and I believe we already have a bug about that needing to be supported. Dave
