Subject: Re: [boost] GitHub testing issues
From: stefan (stefan_at_[hidden])
Date: 2018-12-19 18:37:16
On 2018-12-19 1:28 p.m., John Maddock via Boost wrote:
> At the very least someone should quickly survey all the existing CI
> scripts and file PR's against those that need fixing - a mailing list
> announcement that stuff *might* be broken isn't enough IMO.
...and this is one of my biggest annoyances with Boost.Build: the fact
that this isn't a stable (third-party) tool that I can simply rely on,
but rather a (still !) moving target that I need to adjust to regularly
in my projects.
Indeed, I would have expected a change such as the one from Peter to
work with projects whether they added such a yml file or not. (Of
course, the advantage of the chosen strategy is to force everyone
update, keeping things in sync.)
Frankly, pushing such a change onto >150 projects is unacceptable in my
(not so) humble opinion.
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk