On 25 July 2011 12:27, Torfinn Ingolfsen <tin...@gmail.com> wrote:
> My two cents after reading this whole thread:
>
> like it or not, portupgrade is currently the "official" tool (it's in
> the Handbook and all other docs).
> So in my view, this is what needs to be done:
> a) select a new "official tool"
> b) create or update said tool so it is working to 95% of all the wishes
> c) update all the documentation pointing to this new tool, and set a
> warning ("the old tool, portupgrade, is going away in X years")
> d) wait X years
> e) remove portupgrade
>
> As Doug wrote, change is hard. But there is a difference between
> change because all other options has run out of time, and planned
> change.
> We can make it less hard, at the cost of a longer timeframe.The usual process of deprecaction is to add a warning in one release, and then remove it in the next. While I appreciate portupgrade isn't part of the base system, I think this process would be appropriate. Chris _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
