Date: Mon, 10 Feb 2020 20:44:07 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 243649] [patch] devel/libepoll-shim: Update to 0.0.20191117 version to unbreak re-plugging input devices Message-ID: <bug-243649-7141-3DfDXDyacN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243649-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-243649-7141@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=3D243649 --- Comment #17 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Niclas Zeising from comment #15) Thank you for working on this. I think avoiding a build system by forking is not such a great idea, especially since cmake is used by so many ports and one always ends up installing it anyway[0]. If you're really dedicated to keep cmake out, I would suggest to: a) Document this in the porters handbook ("areas of the ports tree that avoid cmake", e.g. dependencies of xorg-server) b) Do the changes necessary for this to happen as patches in the port skeleton and still switch to the original upstream. Then retire our fork. This will remove one indirection that makes it unnecessarily painful and complicated to contribute. c) Make sure `make test` still runs the unit tests The fork has to be maintained. Assuming that epoll-shim isn't abandoned, future changes need to be merged into our fork. If our fork uses a different build system, that's extra work on every update that has to happen before the port can be updated; in a different place, involving different people or at least different communication channels and processes. So this isn't just about this one update, but about every future update down the road. [0] make -C /usr/ports search bdeps=3Dcmake display=3Dname --=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-243649-7141-3DfDXDyacN>