Well, I think the point is to have KiCad at bleeding edge, but not every dependency library. As long as there are no known issues with an old boost, et. al., why should you want to be also at bleeding edge of those?
Updating everything frequently just makes it harder to see if issues are in KiCad or in an updated dependency. And wrt to features Adam already told that he will be working on providing a scripting enabled build next. Regards, Bernhard > On 22 Feb 2015, at 20:31, Bob Gustafson <[email protected]> wrote: > > I am thinking that the point of 'Nightlies' is to build at the 'bleeding > edge' and provide the builds to folks who can then easily try their normal > working 'use case' to see if things (still) work. If they crash - fine, we > have a data point. > > Looking at the Version info of the current 'Nightlies', I see boost still at > 1.54, and many of the environmental variables turned 'off'. The source code > version does seem pretty close to the repository revno, but do the added > patches affect things that are not turned 'on' by the environment variables? > > Just a thought. > > Bob G > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
