BIND 10 #2367: select features to build and install
BIND 10 Development
do-not-reply at isc.org
Mon Oct 7 14:17:24 UTC 2013
#2367: select features to build and install
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: kean
Type: task | Status:
Priority: medium | reviewing
Component: build system | Milestone:
Keywords: | Sprint-20131015
Sensitive: 0 | Resolution:
Sub-Project: Core | CVSS Scoring:
Estimated Difficulty: undecided | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by kean):
Only three comments. First, do you want to handle the case where a user
just specifies "--enable-components" with no argument? If so the
$enableval is "yes" and should probably behave the same as "all".
Second, since --enable-dhcp forces --enable-libdhcp, you will want to
conditionalize the setting of enable_libdhcp rather than just setting to
it $enableval, otherwise a misguided user could --enable-dhcp --disable-
libdhcp. Also, setting enable_libdhcp on line 28 is redundant since it is
set on line 35.
Third, not all of the components you can specify in --enable-components
have their own distinct --enable-whatever option, and the doc string for
--enable-components does not list the full valid list of components. You
would have to look at the configure script to see what they all are. Was
that intentional? Is this mainly for internal use? If we expect customers
to be able to truly cherry-pick what gets built the doc string should
contain the valid list. If you don't want to add --enable-whatever options
for each component then I suggest that none of them have it, else it is a
bit inconsistent.
--
Ticket URL: <http://bind10.isc.org/ticket/2367#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list