Closed sveneh closed 9 years ago
Dependency management is already integrated into the CI, with forced builds only and rightfully so. There's no silver bullet to changing or new dependencies. For example, adding libm (let's say there's no ubuntu package), it'll need another builder in the buildbot's config (which can't be automated), a new debian folder branch with new control/rules/change files (also impossible to automate the creation of that), adding a brew formula (also, no automation possible), and so on. Same thing for Windows. Unless you can program a bot that can code for us, at which point none of us would have to do anything anymore, there is simply no solution to this. Those are the present limits of automation regarding dependencies. Closing this until the singularity reaches us.
@caktux I get your point, but this is not what I'm heading for. Anyway this is a low priority issue and not important right now. I just want to keep it for my reference.
For a full continuous deployment process dependency management should be integrated into the CI server.
Something in the line like https://docs.google.com/a/ethdev.com/document/d/1eg9gKobQwJ6jn6qmD6HTPB3Pm5VOTdWy93cWNWGlf5c/edit#