On Thu, Jun 25, 2009 at 02:00:12PM -0500, Nicolas Williams wrote: > Well, why stop at obsolescence of the whole pkg? Why not also do this > for any feature removal that doesn't involve pkg removal? I.e., why not > include an action to warn of feature removal? > > Also, should it be possible to warn of future removal? In ARC speak > obsolete means that the feature will be removed in the future. In IPS > speak obsolete seems to mean "has been removed". Is that inconsistency > problematic?
Both of these should be handled separately from package obsolescence by package metadata that contains this information. We already have the notion that a package manifest should contain a list of bugs that were fixed in that package version, and ARC cases that were implemented in that version. Stephen, Bart, and I were talking this morning about adding (if they're not there already) unique IDs to release notes so you could do the same thing there. Then a little bit of magic to figure out the entire set of bug fixes, projects, and EOF (and other) notices on the arc you're upgrading along, and voila, you have a customized set of release notes for the upgrade you just did (or are about to do). Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
