From owner-svn-src-head@freebsd.org Wed Feb 1 23:26:22 2017 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36E95CCC7B5; Wed, 1 Feb 2017 23:26:22 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13C751747; Wed, 1 Feb 2017 23:26:22 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 5E93E39E0; Wed, 1 Feb 2017 23:26:21 +0000 (UTC) Date: Wed, 1 Feb 2017 23:26:21 +0000 From: Alexey Dokuchaev To: Mark Linimon Cc: Slawa Olhovchenkov , src-committers , John Baldwin , "svn-src-all@freebsd.org" , Takahashi Yoshihiro , "svn-src-head@freebsd.org" , Warner Losh Subject: Re: svn commit: r312910 - in head: . etc/etc.pc98 etc/rc.d lib/libsysdecode libexec release release/doc release/doc/en_US.ISO8859-1/hardware release/doc/en_US.ISO8859-1/readme release/doc/share/example... Message-ID: <20170201232621.GA20035@FreeBSD.org> References: <201701280222.v0S2MFSR022477@repo.freebsd.org> <3458844.3oruRKbrzH@ralph.baldwin.cx> <20170201103555.GA79121@zxy.spb.ru> <12386326.7GSpFTXsMZ@ralph.baldwin.cx> <20170201170950.GF79121@zxy.spb.ru> <20170201213956.GA3765@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170201213956.GA3765@lonesome.com> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2017 23:26:22 -0000 On Wed, Feb 01, 2017 at 03:39:57PM -0600, Mark Linimon wrote: > On Wed, Feb 01, 2017 at 08:09:50PM +0300, Slawa Olhovchenkov wrote: > > Also, I am think current ports don't build on 4.x. > > I will personally guarantee, in writing, that current ports do not build > on 4.x, nor have they done so for years. I personally removed the legacy > cruft when 4.11 finally went EOL. They don't build as is, but they still can be tamed (patched) to build and install nicely on 4.x with some effort. Most remaining 4.x installations are server ones which typically carry a well known selection of ports that are not hard to maintain locally for 4.x compatibility. One does not have to have *entire* tree to build flawlessly on 4.x. > > I am got complains about using ports on 8.x. > > I am 99% certain that ports will not work on either 8.x or 9.x. Legacy > cruft was removed at the EOL in each of those cases. That's quite wrong actually: most ports build and run just fine on 8.x (X.org stack is one major exception), with some fairly trivial changes. > Anyone who think that we can support ports on 4.x, 5.x, 6.x, 7.x, 8.x, > 9.x, 10.x, 11.x, and -current, all at the same time, needs to seek medical > attention at once. Well, we're doing something more than devoid any support claims: we're deliberately breaking it, often for little to no reason. Things like r431746 are disgrace to FreeBSD and utter disrespect to our users. :-( > At the absolute least, that era spans 3 major versions of make(1) and > two completely different package implementations. That's largely irrelevant and hardly ever causing problems. All needed make(1) implementations are available in ports; I can still build modern ports in 8.x tinderbox with WITH_PKGNG=yes/PKGSUFFIX=.txz. ./danfe