Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • I second that, you should be able to easily fetch the source of the library version you are using. Why on earth do you need the "ultimate bleeding edge version" of the library? It just adds potential entropy to the project.. Commented Feb 29, 2012 at 17:11
  • 1
    I agree only partly. IMHO it depends on the development policy for the lib. If the lib is under active development of a second team, you are 100% right. If the lib can be changed by anyone of the current team AND if the policy is that the lib should be kept backwards compatible in any way, then using the always the newest version helps to identify integration problems more early, which is a good thing. Commented Feb 29, 2012 at 17:54
  • Doc Brown - I agree. My answer was based on the fact that the question was phrased such that the only reason for requiring the get & compile was so that developers could read the source code. Commented Feb 29, 2012 at 18:49