Currently, if user installs by AI with default manifest,
latest bits are pulled from given IPS repository.
It seems that one of the scenarios people are interested
in is to install particular build which is not the latest one.
Following list of packages installed by default
(when using default manifest) is for now in that order:
SUNWcsd
SUNWcs
babel_install
entire
If user wants to install particular build, it is necessary
to append version to those packages and make sure 'entire'
goes first.
And as David Comay pointed out, it will be easier starting
build 110, since only 'entire' will have to be appended with
build leaving rest of the packages as they are:
entire at 0.5.11-0.<build #>
SUNWcsd
SUNWcs
babel_install
The problem with our current default manifest is that entire
is last package and if user just appends package version,
the installation fails - e.g (bug 7784).
...
pkg: pkg: the following package(s) violated constraints:
"Package entire contains constraint that requires downgrade of
installed pkg pkg:/SUNWlxml at 2.6.31 <mailto:SUNWlxml at
2.6.31>,5.11-0.110:20090320T182511Z:
Pkg SUNWlxml: Optional min_version: 2.6.31,5.11-0.108 max
version: 2.6.31,5.11-0.108 defined by: pkg:/entire
Unable to install entire at 0.5.11 <mailto:entire at 0.5.11>,5.11-0.108 in /a
om_perform_install failed with error 114
Auto install failed
Automated Installation failed - error 255
...
Based on this, I am thinking if it might make sense to reorder
packages in default manifest, so that people don't run into this
kind of problems when they neglect (or don't know it is needed)
to reorder packages.
Also, given the fact that people are interested in this use case,
I am wondering if it might be reasonable to capture this as one
of scenarios in AI doc.
Any comments are highly appreciated.
Thank you very much in advance,
Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090330/377f0b31/attachment.html>
