From owner-freebsd-ports@FreeBSD.ORG Fri Jun 6 07:29:04 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 10FFFC9F for ; Fri, 6 Jun 2014 07:29:04 +0000 (UTC) Received: from nschwmtas06p.mx.bigpond.com (nschwmtas06p.mx.bigpond.com [61.9.189.152]) by mx1.freebsd.org (Postfix) with ESMTP id 9BCD32F0B for ; Fri, 6 Jun 2014 07:29:03 +0000 (UTC) Received: from nschwcmgw06p ([61.9.190.166]) by nschwmtas06p.mx.bigpond.com with ESMTP id <20140606072854.HOPH3884.nschwmtas06p.mx.bigpond.com@nschwcmgw06p>; Fri, 6 Jun 2014 07:28:54 +0000 Received: from hermes.heuristicsystems.com.au ([121.210.107.100]) by nschwcmgw06p with BigPond Outbound id AvUt1o00k29zwdD01vUtBQ; Fri, 06 Jun 2014 07:28:54 +0000 X-Authority-Analysis: v=2.0 cv=Pdd9d1dd c=1 sm=1 a=SEJ2iDwVkb98DYvesvueMw==:17 a=JipEcVzqA9wA:10 a=8nJEP1OIZ-IA:10 a=GHIR_BbyAAAA:8 a=ayC55rCoAAAA:8 a=6I5d2MoRAAAA:8 a=M2qWvyKHfs8s41LITLYA:9 a=wPNLvfGTeEIA:10 a=SV7veod9ZcQA:10 a=SEJ2iDwVkb98DYvesvueMw==:117 Received: from [10.0.5.3] (ewsw01.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.14.5/8.13.6) with ESMTP id s567Rxog022308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 6 Jun 2014 17:28:00 +1000 (EST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Message-ID: <53916D7E.5030508@heuristicsystems.com.au> Date: Fri, 06 Jun 2014 17:27:58 +1000 From: Dewayne Geraghty User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Paul Schmehl Subject: 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 Content-Transfer-Encoding: 7bit Cc: Erich Dollansky , 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: Fri, 06 Jun 2014 07:29:04 -0000 On 6/06/2014 11:05 AM, 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. > > Erich > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > Paul, I would echo Enrich's advise. Occassionally over the last 18 months my ports tree build (of 487 ports) would fail. A workaround, for me, was to update the ports tree and then revert /usr/ports/Mk - sometimes I'd search through the svn logs for a clue, but more recently I'd revert a week at a time. This being done to get something urgent out of the way until a PR or fix was acted upon, and the folks supporting ports meta-system are extremely responsive. Of course if a port needs something that was changed under /usr/ports/Mk then you'll probably have to revert the port as well and change the VERSION info as needed - this is time-consuming and you really need to set aside some time for testing. Its a real kludge but if you're stuck... As I recall the change to ports to use a different make was tied to EOL for 8.3, seems reasonable though something of a paradigm shift for ol' timers (I'm a 2.2.5 person) that are used to building ports on a system long after the base system has been EOL. However it does lend itself to the argument that if changes to the ports system is tied to the base operating system, then the meta-ports ie /usr/ports/Mk should also. Unfortunately release management of the ports meta-system, after a decade, remains elusive. Though it should be noted that preparatory communication is improving - thanks to the team and Eitan's contributions. During some side-conversations I was surprised to learn that there is some back-porting of fixes taking place in the ports branches ref: http://svnweb.freebsd.org/ports/branches/2014Q2/ (thanks to Guido for bringing that to our attention). So maybe this is your starting point and svn update the particular ports you require is another option (as a temporary workaround)? Dewayne.