> Which is why ui_msg is not deprecated, there are no plans to remove it from > MacPorts base, and not every instance of ui_msg in every port should be > replaced with notes.
:-) That's why the original message was suffixed with "where applicable." The ones that use ui_msg as notes could/should use notes. > I'm not sure how best to handle these situations using notes. The best I've > thought of is to define the notes normally, then in pre-activate, clear the > notes if the user has already dealt with what they tell the user to do. That > way "port notes" still works, but the notes don't get shown to the user every > time they upgrade. But I haven't tested this strategy in practice. Ryan, I suggest clearing the notes out during a later phase: as we've seen with KDE ports users may build them phase-by-phase. If configure phase is already done then the message won't be cleared. Right?
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
