Date: Thu, 03 Jun 2021 21:03:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 256369] games/lbreakout2 is out-of-date Message-ID: <bug-256369-7788-p81rRVwRpr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256369-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-256369-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256369 --- Comment #2 from Christopher <inbox@alleghenycomputer.com> --- Thanks for the feedback... Looking back on this, my description was poorly worded and I apologize. It's not that the port is out of date as you point out; it's that the "auth= or" of LBreakout2 has publicly announced that he is not maintaining this anymor= e. Instead, is directing people to the newer and maintained LBreakoutHD. (listed in bold red here: https://lgames.sourceforge.io/LBreakout2/ ) I am all for leaving older, unmaintained software around... as such things = can still help users. I just get confused as I keep tripping over ports that are dropped quickly because upstream has discontinued support and yet other's don't get dropped. And, again I am fine with that... I just don't understood where the line is drawn as it seems to be both very stringent and yet flexible all at the same time. But... I am interested in learning, so I'll see what I can do with the port= er's handbook. Thanks again and I will close this PR. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256369-7788-p81rRVwRpr>