From owner-freebsd-ports@FreeBSD.ORG Mon Jun 9 02:44:19 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14139D82 for ; Mon, 9 Jun 2014 02:44:19 +0000 (UTC) Received: from luigi.brtsvcs.net (luigi.brtsvcs.net [204.109.60.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E64E22070 for ; Mon, 9 Jun 2014 02:44:18 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:880:bd0:21c:c0ff:fe7f:96ee]) by luigi.brtsvcs.net (Postfix) with ESMTPSA id 8044A2D4F9F; Sun, 8 Jun 2014 19:37:02 -0700 (PDT) Received: from [IPv6:2601:7:2280:38b:a8db:487d:2904:a375] (unknown [IPv6:2601:7:2280:38b:a8db:487d:2904:a375]) by chombo.houseloki.net (Postfix) with ESMTPSA id 477D854F; Sun, 8 Jun 2014 19:36:59 -0700 (PDT) Message-ID: <53951DC9.9030604@bluerosetech.com> Date: Sun, 08 Jun 2014 19:36:57 -0700 From: Darren Pilgrim Reply-To: FreeBSD Ports User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Erich Dollansky Subject: RELEASE_x_y_EOL ports tags [Was: Re: Who was the mental genius] References: <20140606090550.0d1a8510@X220.alogt.com> In-Reply-To: <20140606090550.0d1a8510@X220.alogt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 02:44:19 -0000 On 6/5/2014 6:05 PM, Erich Dollansky wrote: > Hi, > > On Thu, 05 Jun 2014 15:09:53 -0500 > Paul Schmehl wrote: > >> That decided it was a good idea to completely break ports to force >> people to upgrade? You couldn't come up with a warning system >> instead of outright breaking ports? The idiots are apparently >> running the asylum. {{sigh}} >> > > this is the reason why I am asking for versions on the ports tree since > a decade. Ok, we have the revision now. Just go back in the revision > until it works. It is a good practice to make a note of the revision of > the running ports tree you have before updating it. We do have that. We have RELEASE_X_EOL tags that identify the last known-good ports tree for a given major branch. Unfortunately, this time the break happened in the middle of the 8.x lifespan, so there is no handy EOL tag. Perhaps a RELEASE_x_y_EOL tag would be a useful thing to add whenever there is a break like this? It certainly would be an easier mnemonic to say "check out the RELEASE_8_3_EOL tag" instead of "check out R112358". Hell, the prior's even self-documenting if someone happened to stumble across http://svnweb.freebsd.org/ports/tags/. We already have tags going back through 20 years of releases (just in case you want a ports tree that works with release 2.0.5) and an established policy of tagging for "last known good" at the major level. I don't think a few more tags are going to hurt if it saves someone the hassle of dancing up to the line of an API/ABI break.