Re: git: 4a384fbfb20b - main - accessibility/redshift: Deprecate and set expiration date to 2024-06-30

From: Michael Gmelin <grembo_at_freebsd.org>
Date: Fri, 07 Jun 2024 07:40:40 UTC

On Thu, 6 Jun 2024 21:47:17 -0700
Kevin Bowling <kevin.bowling@kev009.com> wrote:

> On Thu, Jun 6, 2024 at 9:01 PM Alexey Dokuchaev <danfe@freebsd.org>
> wrote:
> >
> > On Thu, Jun 06, 2024 at 07:07:53PM +0000, Daniel Engberg wrote:  
> > > commit 4a384fbfb20b4d684f86aa3af1f898abf809ed49
> > >
> > > accessibility/redshift: Deprecate and set expiration date to
> > > 2024-06-30
> > >
> > > No upstream activity for the past 4 years, a lot of bug reports
> > > upstream  
> >
> > Could you please stop arbitrarily deprecating working software?
> > Lots of us use redshift as their daily driver because of its
> > flexibility and don't really care what happens upstream or whether
> > it supports something as useless as Wayland.  
> 
> I do not use this software but that is beside the point and I agree in
> principle that there seems to be an overeagerness in deprecating ports
> recently.  If the software is building, and is not retarding progress
> elsewhere, there should be no impetus to go hunting for ports even if
> they seem less useful than alternatives.  If there is some other
> technical concern driving this like disk space or build time please
> communicate that to ports-developers so it can be debated against
> other options.
> 
> > > Redirect users to accessibility/sct  
> >
> > Simplistic program which doesn't even parse command line to give one
> > usage information, and "last commit 5 years ago" doesn't bother you
> > in this case for some reason.  Surely there won't be lots of bug
> > reports because there ain't much no features.
> >
> > Lewis, could you chime in and restore the previous status quo?
> >
> > ./danfe  

Just as a datapoint, I'm also using redshift and it works just fine for
me.

Cheers

-- 
Michael Gmelin