head 1.3; access; symbols pkgsrc-2023Q4:1.3.0.52 pkgsrc-2023Q4-base:1.3 pkgsrc-2023Q3:1.3.0.50 pkgsrc-2023Q3-base:1.3 pkgsrc-2023Q2:1.3.0.48 pkgsrc-2023Q2-base:1.3 pkgsrc-2023Q1:1.3.0.46 pkgsrc-2023Q1-base:1.3 pkgsrc-2022Q4:1.3.0.44 pkgsrc-2022Q4-base:1.3 pkgsrc-2022Q3:1.3.0.42 pkgsrc-2022Q3-base:1.3 pkgsrc-2022Q2:1.3.0.40 pkgsrc-2022Q2-base:1.3 pkgsrc-2022Q1:1.3.0.38 pkgsrc-2022Q1-base:1.3 pkgsrc-2021Q4:1.3.0.36 pkgsrc-2021Q4-base:1.3 pkgsrc-2021Q3:1.3.0.34 pkgsrc-2021Q3-base:1.3 pkgsrc-2021Q2:1.3.0.32 pkgsrc-2021Q2-base:1.3 pkgsrc-2021Q1:1.3.0.30 pkgsrc-2021Q1-base:1.3 pkgsrc-2020Q4:1.3.0.28 pkgsrc-2020Q4-base:1.3 pkgsrc-2020Q3:1.3.0.26 pkgsrc-2020Q3-base:1.3 pkgsrc-2020Q2:1.3.0.22 pkgsrc-2020Q2-base:1.3 pkgsrc-2020Q1:1.3.0.2 pkgsrc-2020Q1-base:1.3 pkgsrc-2019Q4:1.3.0.24 pkgsrc-2019Q4-base:1.3 pkgsrc-2019Q3:1.3.0.20 pkgsrc-2019Q3-base:1.3 pkgsrc-2019Q2:1.3.0.18 pkgsrc-2019Q2-base:1.3 pkgsrc-2019Q1:1.3.0.16 pkgsrc-2019Q1-base:1.3 pkgsrc-2018Q4:1.3.0.14 pkgsrc-2018Q4-base:1.3 pkgsrc-2018Q3:1.3.0.12 pkgsrc-2018Q3-base:1.3 pkgsrc-2018Q2:1.3.0.10 pkgsrc-2018Q2-base:1.3 pkgsrc-2018Q1:1.3.0.8 pkgsrc-2018Q1-base:1.3 pkgsrc-2017Q4:1.3.0.6 pkgsrc-2017Q4-base:1.3 pkgsrc-2017Q3:1.3.0.4 pkgsrc-2017Q3-base:1.3 pkgsrc-2017Q2:1.2.0.4 pkgsrc-2017Q2-base:1.2 pkgsrc-2017Q1:1.2.0.2 pkgsrc-2017Q1-base:1.2 pkgsrc-2016Q4:1.1.0.8 pkgsrc-2016Q4-base:1.1 pkgsrc-2016Q3:1.1.0.6 pkgsrc-2016Q3-base:1.1 pkgsrc-2016Q2:1.1.0.4 pkgsrc-2016Q2-base:1.1 pkgsrc-2016Q1:1.1.0.2 pkgsrc-2016Q1-base:1.1; locks; strict; comment @# @; 1.3 date 2017.09.06.14.14.31; author taca; state Exp; branches; next 1.2; commitid FRihKxonSV5JW86A; 1.2 date 2017.03.19.16.34.30; author taca; state Exp; branches; next 1.1; commitid Wg5y0GLPvgbxdbKz; 1.1 date 2016.03.03.14.37.46; author jmmv; state Exp; branches; next ; commitid PlvxcbG6D82LOcXy; desc @@ 1.3 log @Update ruby-rb-fsevent to 0.10.2. v0.10.2 2017/07/01 While procs are flexible about arity, lambdas and converted methods are not. Thus passing in two parameters broke any such callbacks. The only change in this release is that callback block arity is checked before passing in any values. v0.10.1 2017/06/30 * rebuilt fsevent_watch against 10.8 * fixed documentation v0.10.0 2017/06/30 * MacOS 10.13 specific flags added to compatibility code * Added second parameter to callback with more detailed event info * Switched communication format to OTNetstrings, fixing a bug where some events were ignored if they contained certain characters * Removed custom path fixture from tests as there have been complaints about using the gem with maven (??) @ text @@@comment $NetBSD: PLIST,v 1.2 2017/03/19 16:34:30 taca Exp $ ${GEM_HOME}/cache/${GEM_NAME}.gem ${GEM_LIBDIR}/Gemfile ${GEM_LIBDIR}/Guardfile ${GEM_LIBDIR}/LICENSE.txt ${GEM_LIBDIR}/README.md ${GEM_LIBDIR}/Rakefile ${GEM_LIBDIR}/bin/fsevent_watch ${GEM_LIBDIR}/ext/LICENSE ${GEM_LIBDIR}/ext/fsevent_watch/FSEventsFix.c ${GEM_LIBDIR}/ext/fsevent_watch/FSEventsFix.h ${GEM_LIBDIR}/ext/fsevent_watch/TSICTString.c ${GEM_LIBDIR}/ext/fsevent_watch/TSICTString.h ${GEM_LIBDIR}/ext/fsevent_watch/cli.c ${GEM_LIBDIR}/ext/fsevent_watch/cli.h ${GEM_LIBDIR}/ext/fsevent_watch/common.h ${GEM_LIBDIR}/ext/fsevent_watch/compat.c ${GEM_LIBDIR}/ext/fsevent_watch/compat.h ${GEM_LIBDIR}/ext/fsevent_watch/defines.h ${GEM_LIBDIR}/ext/fsevent_watch/main.c ${GEM_LIBDIR}/ext/fsevent_watch/signal_handlers.c ${GEM_LIBDIR}/ext/fsevent_watch/signal_handlers.h ${GEM_LIBDIR}/ext/rakefile.rb ${GEM_LIBDIR}/lib/otnetstring.rb ${GEM_LIBDIR}/lib/rb-fsevent.rb ${GEM_LIBDIR}/lib/rb-fsevent/fsevent.rb ${GEM_LIBDIR}/lib/rb-fsevent/version.rb ${GEM_LIBDIR}/rb-fsevent.gemspec ${GEM_HOME}/specifications/${GEM_NAME}.gemspec @ 1.2 log @Update rb-fsevent to 0.9.8. v0.9.8 * fsevent_watch : Fix "zombie" processes not dying (#62) @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.1 2016/03/03 14:37:46 jmmv Exp $ d24 1 @ 1.1 log @Initial addition of ruby-rb-fsevent-0.9.7: Ruby interface to the Mac OS X FSEvents API. @ text @d1 1 a1 1 @@comment $NetBSD$ d21 2 @