Jason L Tibbitts III <tibbs(a)math.uh.edu> writes:
"CS" == Christopher Stone <chris.stone(a)gmail.com>
CS> Shouldn't this be: ban use of
CS> Requires(RandomCrapWhichIsntSupportedYet) Otherwise, I can just
CS> change my Requires(hint) to Requires(opt) or some other random
It would be disappointing to have to go to this level of lawyering.
mean, who would actually do that?
*Everyone* is only one typo away from invoking Requires(randomcrap).
ISTM this is not a policy problem. The correct response to this is
to fix our tools so that you get an error if the parenthesized string
isn't one of the accepted values.
If the tools enforce a list-of-accepted-values that's a bit stricter
than upstream's, that's fine too; but what the heck are we doing
allowing obvious mistakes in specfiles to pass?
regards, tom lane