DIP 1028 @safe by default: compilability list of all dub packages

[Jon Degenhardt]

On Tuesday, 7 January 2020 at 16:45:09 UTC, Atila Neves wrote:
> On Tuesday, 7 January 2020 at 11:12:28 UTC, WebFreak001 wrote:
>> On Tuesday, 7 January 2020 at 10:43:44 UTC, Atila Neves wrote:
>>> On Monday, 6 January 2020 at 23:05:29 UTC, WebFreak001 wrote:
>>>>> [...]
>>>>
>>>> Update:
>>>> now built using
>>>> phobos commit c039fed84 (std.bitmanip.bitfields issues fixed)
>>>> dmd commit 0ab7e90df (changes delegate to @safe by default)
>>>>
>>>> [...]
>>>
>>> There are still false negatives - autowrap definitely builds.
>>
>> Running pre-generate commands for autowrap:pynih...
>> make: Entering directory 
>> '/srv/http/org.webfreak.symbols/clones-2020-01-04_00-35-08/5dafbb00bce0bf24b5b71996-autowrap/pynih'
>> make: 'source/python/raw.d' is up to date.
>> make: Leaving directory 
>> '/srv/http/org.webfreak.symbols/clones-2020-01-04_00-35-08/5dafbb00bce0bf24b5b71996-autowrap/pynih'
>> Invalid source/import path: 
>> /srv/http/org.webfreak.symbols/clones-2020-01-04_00-35-08/5dafbb00bce0bf24b5b71996-autowrap/python/source
>> Invalid source/import path: 
>> /srv/http/org.webfreak.symbols/clones-2020-01-04_00-35-08/5dafbb00bce0bf24b5b71996-autowrap/python/source
>> Invalid variable: PYTHON_LIB_DIR
>
> Ah. I guess this project assumes that every project can be 
> built/tested with dub as-is (dub build / dub test). For the 
> ones with .travis.yml files it might be worth parsing the YAML 
> and running the "script" section instead (it'll usually be dub 
> test anyway).

The CI system has entries for custom build instructions 
(https://github.com/dlang/ci/blob/master/buildkite/build_project.sh#L124). Something similar could work for this. If available in a public repo then project owners could submit the instructions for their own repos.

Such a setup could also provide a place to add projects that 
don't have dub entries. tilix, onedrive, and sambamba, are highly 
starred github projects that don't have dub entries. Including a 
few of these would be ideal. Of course, this would raise the cost 
of running building and running the tests.

A perhaps cheaper option would be to setup special builds of the 
CI buildkite tests that turn on safety by default. A much smaller 
set of projects, but would provide more detailed info.