Hiya, thanks for the response. Here's what i've done.

Downloaded "kicad-2009-02-26-final-UBUNTU_8.10.tgz" from KiCad website.

Used Archive Manager to extract "kicad" folder to desktop.

Opened Rootterminal to move "kicad" folder from desktop to "usr/local/" with 
"sudo mv kicad/ usr/local/

Then copied "kicad.desktop" from "usr/local/kicad/bin/kicad/ to desktop (kicad 
icon appears on desktop!)

NOTE: Files in usr/local/ are unaffected by updates, so libraries will remain. 
Also, i now have permission to edit/add libraries.

Thank you.

--- In [email protected], Dimitris Lampridis <d.lampri...@...> wrote:
>
> On Sun, 03 Jan 2010 17:27:31 -0000
> "Werner" <wernervanderstra...@...> wrote:
> 
> > 
> > Hello, i'm running Ubuntu Karmic Koala.
> > I've installed KiCad via the Ubuntu Software Centre.
> > Next i create a new part in the current loaded library.
> > Then i try to update the library file but get an error:
> > 
> > not possible because no access to file
> > 
> > This is because the library is in usr/share/KiCad/Library.
> > And this is a root owned folder.
> > 
> > When i remove KiCad from the system via the Ubuntu Software Centre,
> > the KiCad folder with content remains in usr/share/
> > 
> > Would it be safe to change the ownership from root to my personal
> > login?
> > 
> > How did you install KiCad without losing permission to make changes
> > to the library folder?
> > 
> > Thanks...
> > 
> 
> Dear Werner,
> 
> Modifying directly the /usr/share/kicad files, either as root or by
> changing folder permissions is dangerous, not because of security, but
> because your Ubuntu installation will overwrite your modified files
> in case a newer "kicad" package is introduced in the Ubuntu
> repositories. As a result, the package upgrade will erase all of your
> custom components, replacing the files with the new ones from the
> package.
> 
> Therefore, IMO, it is much better to make your own libraries of custom
> components somewhere within your home folder, or something
> like /usr/local, where your operating system cannot interfere. 
> 
> Cheers,
> Dimitris
>


Reply via email to