Date: Thu, 20 Oct 2016 08:43:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 213587] net-p2p/go-ethereum: Update to 1.4.18 Message-ID: <bug-213587-13-3uHRN8BT4k@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213587-13@https.bugs.freebsd.org/bugzilla/> References: <bug-213587-13@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=3D213587 --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Fynn from comment #4) Yes, except in an OPTIONS_GROUP you can add a GROUP_DESC for the group description. Regarding your second goal, the following (from Mk.bsd.options.mk) can be u= sed: # ${opt}_IMPLIES - When opt is enabled, options named in IMPLIES will # get enabled too. There is an opposite=20 # ${opt}_PREVENTS - When opt is enabled, if any options in PREVENTS are # also enabled, it will produce an error. HOWEVER, in this case a UTILITIES option whilst keeping all the other individual options as well is very likely to be confusing because OPTION_IMPLIES and OPTION_PREVENTS do *not* auto-select the options in the user-visible interface, it happens in the background.=20 I would choose between: 1) *one* UTILITIES option that installs all optional ones, make UTILITIES an OPTIONS_DEFAULT (so package users get them), or 2) keep them as separate options.=20 If it were me, I'd choose (1) (one UTILITIES or TOOLS or EXTRAS option), as= per my reasoning in comment 3 --=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-213587-13-3uHRN8BT4k>