Date: Fri, 07 Dec 2018 08:16:49 +0000 From: bugzilla-noreply@freebsd.org To: elastic@FreeBSD.org Subject: [Bug 233843] sysutils/logstash5: logstash-plugin binary is not executable Message-ID: <bug-233843-37421-vf5bG4Jm9e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233843-37421@https.bugs.freebsd.org/bugzilla/> References: <bug-233843-37421@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=3D233843 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Summary|sysutils/logstash5 |sysutils/logstash5: |bin/logstash-plugin not |logstash-plugin binary is |executable |not executable Severity|Affects Some People |Affects Many People Flags| |merge-quarterly? Keywords| |needs-patch, needs-qa --- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> --- If a better alternate method within the context of the build system (such a= s a bug fix) is not possible/feasable, the workaround the manually modify the executables permissions should: - Use the ${CHMOD} variable provided by the framework - Use ${LOCALBASE} / PREFIX-safe variable for the path - Happen at post-install: stage (in STAGEDIR} However, the port already includes the following block in do-install: for x in ${LOGSTASH_BIN_FILES} @${CHMOD} ${BINMODE} ${STAGEDIR}${LOGSTASH_DIR}/bin/${x} But LOGSTASH_BIN_FILES only contains 'logstash' The sysutils/logstash6 port takes a more robust approach, but chmod'ing all binaries in the path: ${CHMOD} ${BINMODE} ${STAGEDIR}${LOGSTASH_DIR}/bin/* I recommend taking the latter (logstash6) approach in this port. --=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-233843-37421-vf5bG4Jm9e>