Date: Wed, 06 May 2020 02:16:23 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 244239] ports-mgmt/portlint: strange output for security/p5-IO-Socket-SSL Message-ID: <bug-244239-7788-7Avz1bRLlA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244239-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-244239-7788@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=3D244239 --- Comment #7 from Sergei Vyshenski <svysh.fbsd@gmail.com> --- Marcus, This time portlint becomes very tolerant to=20 1) order of RUN_ and BUILD_ , and to=20 2) "use then assign" for variables. Point 2 is too common of practice in typical Makefile of port (consider inc= lude of bsd.port.mk in the last section of Makefile), and moreover - inside typi= cal Mk/*.mk. What do you think of demanding one of two reasonable approaches (see 5.9.2. "RUN_DEPENDS" from Porter's Handbook), each of which respects correct version of points 1) and 2) above: (approach A)=20 MY_DEPENDS=3D ...explicit list... BUILD_DEPENDS=3D ${MY_DEPENDS} RUN_DEPENDS=3D ${MY_DEPENDS} (approach B) BUILD_DEPENDS=3D ...explicit list for build... RUN_DEPENDS=3D ...explicit list for run... As for Perl ports which you mention, maybe they could be promoted to a new standards via automatic blanket commit? Regards, Sergei --=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-244239-7788-7Avz1bRLlA>