BIND 10 #1041: BIND10 build fails if a directory in the path has spaces
BIND 10 Development
do-not-reply at isc.org
Fri Aug 26 12:36:19 UTC 2011
#1041: BIND10 build fails if a directory in the path has spaces
-------------------------------------+-------------------------------------
Reporter: cas | Owner: vorner
Type: | Status: reviewing
defect | Milestone:
Priority: major | Sprint-20110830
Component: | Resolution:
configuration | Sensitive: 0
Keywords: | Sub-Project: Core
Defect Severity: | Estimated Difficulty: 3.0
Medium | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by vorner):
Hello
Replying to [comment:14 jelte]:
> I didn't use -q because it is not supported on all systems (even though
it's part of posix, our default solaris grep doesn't support it, for
instance. posix my %ss).
Ah, crap.
We could use test -z "`echo | grep`" instead to avoid using any
parameters, but it's not important.
> I'm sure we can come up with a cleaner one than my proposal, but I must
say I am not a fan of the second either, it makes misuse of being badly
quoted, which I understand is the exact goal, but relying on such an error
failing nicely as it were sounds brittle IMO
OK, I see. We could try to sandbox the shell failing somehow (eg. running
it in subshell and redirecting its outputs, etc), but that sounds an
overkill anyway for a thing that will fail anyway. Whoever has newlinest
and {{{`rm -rf /`}}} in the path deserves the punishment.
So, let's merge your version.
--
Ticket URL: <http://bind10.isc.org/ticket/1041#comment:15>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list