dub: should we make it the de jure package manager for D?

[ilya-stromberg]

On Wednesday, 11 September 2013 at 11:31:11 UTC, Faux Amis wrote:
> On 11-9-2013 12:28, ilya-stromberg wrote:
>> On Wednesday, 11 September 2013 at 06:28:30 UTC, Sönke Ludwig 
>> wrote:
>>> Am 11.09.2013 00:06, schrieb luminousone:
>>>> Projects that haven't had an update for an excessive amount 
>>>> of
>>>> time should likely be hidden but still available except in 
>>>> cases
>>>> where it is known to be unchanged without need for 
>>>> updates(such
>>>> as most wrappers).
>>>
>>> Agreed. Maybe some other knowledge, such as how many other 
>>> (active)
>>> packages depend on it, or how often it is still downloaded, 
>>> can help
>>> to get a robust automatic measure.
>>
>> Simple idea: try to build the package via current DMD. If 
>> compilation
>> false then the package too old (or we have DMD regression). 
>> So, it would
>> be nice to have package autotester like for DMD/Phobos 
>> repositories.
>
> This way it actually knows the last compatible dmd version.

Yes. And list of problem packages with compilation errors or 
broken dependencies.