@Anonymous wrote:
Are you planning on updating the macOS installation procedure any time soon?
EAGLE has always been poorly implemented on OS X/macOS with the directory in Applications that contains the actual application and the other lbr/projects/cam etc. directories. This is not how software is installed in macOS and EAGLE is pretty much the only software that does this. It would be much better if the following structure was used:
/Applications/EAGLE
/Users/XXXX/Documents/EAGLE/cam etc.
Having everything in Applications makes it hard for users without admin rights who then can't change library parts etc.
Hi Craig,
This I agree with this, except that version specific ULP and scripts should remain with the version (more below). I think they are moving away from having the libraries all in the EAGLE application folder as the managed libraries feature does in fact put them all elsewhere (but annoyingly there is a copy left in the Application/EAGLE.x.x.x/lbr/ folder which are unused but wasting lots of space.
You can of course move libraries to a new folder in your user area manually (or create your own libraries there) and update the directory setup to point to this user location rather than the EAGLE /Application location, this gets round the issue of non admin users not having rights to update libraries.
@Anonymous wrote:
Also, the updates are very frustrating with a whole new directory structure installed in /Applications each time so we end up with
/Applications/EAGLE-8.2.0
/Applications/EAGLE-8.2.1
/Applications/EAGLE-8.2.2
etc.
I don't see the need to effectively have multiple copies of EAGLE installed rather than a central install that is updated when bug fixes etc. are released.
This I don't agree with. I don't want to have to uninstall and reinstall to get to older versions of the app which I often do if a new version has bugs or I want to see how the behaviour has changed when a new feature has added. Most CAD tools of this type will install new versions into separate folders.
What they could do though is have structure to their version numbering and releases so that if they are for example 8.x.y releases then the application would be say EAGLE-8.x and this would be a release that incorporates new features and then updates which were just bug fixes could be denoted by the y number incrementing. They don't do this currently though and new features end up in the minor number releases. Having said that, v8.2.2 actually was a bug fix release, and I am very pleased about this. Hopefully they'll see the benefit of this and consider having separate feature and bug fix cycles. That way we can end up with new features that have had their bugs fixed before something else is introduced which causes usability regressions meaning we can't make use of the fixed features in the update.
Another solution would be to default to the current option of keeping separate install locations per version but have an option to choose this or "Update in Place" and a checkbox to remember your preference. That way those who think they want update in place can have it work that way and those who don't want that to ever happen can be happy that an update isn't going to leave them having to do extra leg work to roll back versions.
Best Regards,
Rachael
