@Anonymous wrote:
Can previous (older) revisions of managed libraries be referenced and resolved from a given Eagle design?.
Your design at any given revision will contain the library parts as they were at that version it doesn't rely on the existence of the libraries for the design to work. However, the libraries in the design may be older versions so if you then tell it to do an update or try to add a newer version of a part which is already in the design, it'll try and update things for you from the libraries to the newer versions. This is the same situation you would have had if you'd had regular libraries under GIT version control in a separate repository, although I think the managed system makes it more obscure and less simple to resolve.
Personally I don't use managed libraries for my main libraries as the managed system doesn't add anything good in terms of library management, it just makes things more fiddly, and I don't use the standard libraries, I use my own libraries which are developed to my standards. If I want to use the Fusion360 link then I will copy my design and export all the libraries to a single new library, make that managed and then update my copied design with those parts and work in Fusion360 on that copy, but this is also a faff so I don't use the Fusion360 integration very much.
Best Regards,
Rachael
