Are you OK with the new commit log?

>> Usage of ‘false-if-exception’ made me realize that ‘emit-warning’ is not
>> nicely composable.  What about making it return ‘#f’ in order to compose
>> checks and warning together as boolean expressions?  Is that idiomatic?
>> Maybe you have a better suggestion?
>
> Not sure I follow.  Those ‘check’ procedures are only called for effect,
> not for value, right?

My first idea was to have something similar to this kind of
composability...

--8<---------------cut here---------------start------------->8---
  (define (check-texinfo-markup description)
    (or (false-if-exception (texi->plain-text description))
        (emit-warning package
                      (_ "Texinfo markup in description is invalid")
                      'description)))

  (define (check-proper-start description)
    (or (properly-starts-sentence? description)
        (string-prefix-ci? (package-name package) description)
        (emit-warning package
                      (_ "description should start with an upper-case letter or digit")
                      'description)))
--8<---------------cut here---------------end--------------->8---

... but with better semantics.  IMO this would require more deep thought
so let's forget about this for now.  :)

--
Mathieu Lirzin