What is the purpose of this change? In what way will it improve the user experience? Before we ask the package devs to do a lot of work, we might want to dig deeper into the library management issue. I fail to see how installing and likely duplicating the entire KiCad library in the user's home folder solves any of the underlying library management issues in KiCad other than having write access to modify the installed libraries which has its own set of issues. In some respects this has the potential to complicate things even further. I suspect the real issue is out library editing and management tools. I suggest we wait until Orson pushes the symbol library editor to see if this improves the library management situation. Given what I know about it I suspect that it will improve things significant on the library management side of things.
Cheers, Wayne On 11/8/2017 2:02 AM, Oliver Walters wrote: > To the package maintainers: > > For v5 release, can the default library install path be set to a user > directory rather than program directory that may require administrator > rights? > > e.g. instead of > > C:\Program Files\KiCad\share\... > or > /usr/share/kicad/... > > something like; > > C:\Users\Oliver\KiCad\... > > /home/Oliver/KiCad > > (Not necessarily those paths but something like that). > > A lot of users are reporting issues with being able to download or > modify library files, due to user privileges. > > How attainable is such a change before v5 release? > > Thanks, > Oliver > > > _______________________________________________ > 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
