https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235240
--- Comment #6 from Jan Beich <[email protected]> --- (In reply to Sunpoet Po-Chuan Hsieh from comment #5) > Could you please give a case that "consumers may opportunistically > pick it up over kqueue backend or if not required"? Look for ports with CONFIGURE_ENV=ac_cv_header_sys_inotify_h=no. > After this change, do we have to teach every new ports how to find the new > home of inotify.h? No. Only those not using pkg-config. -linotify doesn't exist on Linux, so it always comes with a .pc file (unless older than 20170711). autotools and meson support pkg-config just fine, cmake uses modules to reinvent pkg-config but the support is good if required module exists, gmake and bmake[1] can cache pkg-config output via $(shell ...) and ${SH:!...!}. [1] bmake caching have to be in submake *after* pkg-config is installed as ${SH:!...!} is evaluated at parsing time. gmake isn't affected because it's only used to parse vendor's Makefile while port's Makefile is parsed by bmake. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "[email protected]"
