>>> The second thing is that this code is continuing to use the image >>> object. >> We have REF's logged to get API's to allow us to remove all direct >> access to the image object, as soon as the API's are available we >> will be more than happy to change over to using them. >> > Actually, I looked at the RFE's that I know of this afternoon, and > didn't see this particular issue covered by any of them. I'm aware of > 3 (search, list, authority) and didn't see anything in any of them to > cover this use. Can you please either point me to the fourth (and > others as well if I'm unaware of them) which covers this, or augment > one of the existing ones to make it more clear that this is included > in the bug. My understanding was that the list API should be giving us back the information we are having to fetch directly from the manifests, I'll talk to Michal tomorrow about it to make sure this is covered by the RFE, if not I'll update it.
JR > > Brock >>> The API was designed so that the GUI wouldn't manipulate the >>> image object directly. If you're depending upon behavior in the image >>> object, you'll potentially get broken by an unknown number of changes. >>> If there's functionality that's missing from the API, you should file a >>> bug against the API instead of using the image object directly. >>> >>> -j >>> _______________________________________________ >>> pkg-discuss mailing list >>> [email protected] >>> http://mail.opensolaris.org/mailman/listinfo/pkg-discuss >>> >> >> _______________________________________________ >> pkg-discuss mailing list >> [email protected] >> http://mail.opensolaris.org/mailman/listinfo/pkg-discuss >> > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
