Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Aug 2015 14:05:21 +0200
From:      John Marino <freebsd.contact@marino.st>
To:        Alexey Dokuchaev <danfe@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org>
Cc:        Mathieu Arnold <mat@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r395079 - in head/graphics: . mitsuba mitsuba/files
Message-ID:  <55DDAB81.2030302@marino.st>
In-Reply-To: <20150826114234.GA78599@FreeBSD.org>
References:  <201508230856.t7N8uwal009338@repo.freebsd.org> <96D957F8044D8B647B259802@atuin.in.mat.cc> <20150824070915.GA15244@FreeBSD.org> <20150824084807.GA93486@ivaldir.etoilebsd.net> <20150824090104.GB93486@ivaldir.etoilebsd.net> <20150824094539.GA77434@FreeBSD.org> <20150824102328.GC93486@ivaldir.etoilebsd.net> <20150826114234.GA78599@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 8/26/2015 1:42 PM, Alexey Dokuchaev wrote:
> On Mon, Aug 24, 2015 at 10:53:48AM +0200, John Marino wrote:
>> Not to mention that it's pointless to support earlier than officially
>> supported platforms because everyone else is ripping out support every
>> time they touch a port and see it, actively.  In some cases, the only
>> change in the commit is removing support.  [EOL means EOL.]
> 
> Yeah, I'm worried about this.  I have nothing against removing actual
> cruft -- e.g., BROKEN_FreeBSD_8 statements since they are not really
> breaking anything, just making Makefiles cleaner and easier to maintain.
> 
> Yet I believe it's better to discuss with maintainers when removing the
> actual support.  Maybe it looks different for those OSX-on-their-laptop
> developers, but having all my gear FreeBSD based it usually always an
> unfortunate moment to upgrade.
> 
> People also might argue that breaking ports will urge dumb users like
> myself to upgrade faster.  While this has some merit, let's not forget
> that EOLing the release will cause ports to break by themselves, and
> forcing things does not really change much in the long run, but annoys
> users a lot: no one likes them things are forcibly broken rather then
> being let die teethless in their bed.
> 

Somebody initiates this exact discussion literally every time a platform
falls into EOL.  The most obviously ones when the ports tree is changed
a couple of days after EOL with the knowledge it will break support of
the EOL platform, and then those users of said platform said that was
too aggressive (e.g. they expect gradual bitrot, not full out breakage).

Unfortunately they should expect full out breakage immediately and count
every day that works beyond EOL as a bonus.

IMO, any expectation of "slow-death bitrot" after EOL is unrealistic and
maybe we would do people a better service of dispelling this notion
rather than perpetuating it.  FWIW I don't support removing EOL support
actively (as the only change) but do think it should be removed when
coupled with other maintenance and not just left because it still works
in theory.

John



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55DDAB81.2030302>