>i don't follow you here, the problem is when 2.0.5 builds get some version >"by default" (they don't override it). Those builds would get another version in 2.0.6
I think it simply boils down to what Patrick wrote: "For existing projects in which the workaround was not used, then I would question two things: - Does the project work as expected? - Do they really care what version of D gets pulled in? If they are not using the work around, it seems to me that the answer to at least one of these would have to be 'No'. And in this case, it doesn't seem like altering the behavior matters much anyway." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
