Since in the desktop paradigm, most computers will only have one or 2 users, not all of whom will want custom pieces, how about storing it in a local ".leocad" file in their home directory.
As root, then perhaps they could make global changes, but generally, that would just not be necessary. Cheers, Danny Leonardo Zide wrote: > > I've uploaded a new Linux test binary that can handle piece updates > to the website, it would be great if someone could give it a try and > see if they can use it to import Philo's updates (it worked fine for > me). Make sure you have write permission to the directory where you > have the library installed (usually /usr/local/lib/leocad/), it > currently doesn't show any error messages if you don't but I plan to > add one before I make this version official. > > What's the best way of handling Linux library updates? I know people > won't like if I tell them to run LeoCAD as root and I doubt anyone > wants to make a directory under /usr/local/lib writeable by everyone. > > This binary also includes several bug fixes since the last stable > version was released and the option to export VRML files. I'll upload > a Windows version with the same fixes and features later this week. > > Does anyone have any experience making deb packages? > > Leonardo > > ------------------------------------------------------------------------ > > _______________________________________________ > Leocad mailing list > [email protected] > https://list.gerf.org/listinfo/leocad > _______________________________________________ Leocad mailing list [email protected] https://list.gerf.org/listinfo/leocad
