Date: Thu, 13 Feb 2020 11:27:39 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 243649] [patch] devel/libepoll-shim: Update to 0.0.20200211 version (fixes various problems) Message-ID: <bug-243649-7141-cwxvtI9Nq6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243649-7141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243649 --- Comment #26 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Emmanuel Vadot from comment #25) Thank you for your response. At the moment the author is actively maintaining the software and responds to pull requests and open issues in a timely manner. He was even kind enough to open pull requests against our fork. What I would do is ask him to introduce tagged versions, so portscout can inform us that it's time to update the port. So, unless there is a history of animosities with that specific author, forking an actively maintained project to prepare for him going MIA in the future seems quite unorthodox to me. All it does is create extra work for us and slow down progress. I would only fork once upstream becomes stale or uncooperative. This doesn't seem to be the case here. Assuming there will be an actual need to fork epoll-shim in the future, it might make more sense to do it under github.com/freebsd though, as its usefulness may not be limited to the desktop and having epoll compatibility could be useful when porting all kinds of software from linux. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243649-7141-cwxvtI9Nq6>