Date: Mon, 25 Jul 2011 12:40:41 +0100 From: Chris Rees <crees@freebsd.org> To: Torfinn Ingolfsen <tingox@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: Time to mark portupgrade deprecated? Message-ID: <CADLo839Yun6pvjapOojY=5Lxj43tQKdTVPo_bxWRymEY-kZF5A@mail.gmail.com> In-Reply-To: <CAJ_iqtZY32LtH7axioO%2Be=16BUc1Ufj9cLO=7UecayzPY_D87A@mail.gmail.com> References: <CAF6rxg=TfxbKJwbcm6_c8P7m6%2B-pzvB9SpwKB99%2BLDe4OM%2BeLA@mail.gmail.com> <4E2D1C36.7060400@FreeBSD.org> <1311583851.1812.81.camel@xenon> <4E2D3A84.7020909@FreeBSD.org> <1311588859.1812.104.camel@xenon> <20110725065211.35f2aa7d@seibercom.net> <CAJ_iqtZY32LtH7axioO%2Be=16BUc1Ufj9cLO=7UecayzPY_D87A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 July 2011 12:27, Torfinn Ingolfsen <tingox@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839Yun6pvjapOojY=5Lxj43tQKdTVPo_bxWRymEY-kZF5A>