Shawn Walker wrote: > The version here effectively specifies the initial version of the > configuration to use if one can't be determined from the configuration > file itself. In short, if we specify 3 here, but on load the config > class discovers it's 7, it will auto-correct.
What happens if the class is unable to discover the version because the version is too new and the class can't properly parse the configuration? Thus no auto-correction, and so the version remains, incorrectly, at 3. Does this go into the fallback you mention below based on what paths are there? > This is a fallback path that only happens when we couldn't determine the > version of the image from the configuration file. In the case that you > have a version 7 image that looks like a version 3 image, and we have no > configuration file to tell us otherwise, it seems sane to make > assumptions based on structure in the absence of all other identifying > information. > The only thing I don't like about that message is that it's misleading in > the case that you're updating a user image or an image not rooted at '/' > that you don't have permission to modify. > > Do you still want this message? I don't care too much, so probably "no". Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
