understand, well the solution number two is to just change make install and put the install_manifest.txt outside build. I think a very acceptable solution?
On Wed, Oct 23, 2013 at 9:48 PM, Adam Wolf <[email protected]> wrote: > This will make it easier for me to support multple different Kicads > installed at the same time on a system--so you can have Kicad-GAL and > Kicad-Github and Kicad-GAL-Github, until the item on the CERN roadmap that > moves all that stuff is completed. > > Adam Wolf > W&L > > > On Wed, Oct 23, 2013 at 2:03 PM, Dick Hollenbeck <[email protected]> wrote: >> >> >> Thanks for bringing an understanding to the problem, casting light on it. >> >> >> >> But I think there is just something fundamentally too risky doing >> >> rm -rf <anything> >> >> as root. >> >> So we will have to find a better way. I have wanted to support installing >> on linux into >> home, i.e. ~, and this would remove the need to install as root, or ever >> becoming it. >> >> So I think the real solution will have to wait a couple of weeks. We can >> install into >> home, and let the distro managers install where they want to. >> >> >> >> Dick >> >> >> >> >> >> On 10/23/2013 12:09 PM, Fabrizio Tappero wrote: >> > Dear Dick, >> > Nothing to do with that, the directory I use is the default one >> > ~/kicad-sources. The reason why "sudo rm" it is needed is because the >> > "sudo make install" writes "install_manifest.txt" inside build/ >> > >> > The user is not building any protected dir because sudo is just used >> > in the rm command. >> > >> > by the way, you might want to to change the "make" with "make -j 4". >> > Sensibly faster on modern machines. >> > >> > again, glad to help. >> > Fabrizio >> > >> > On Wed, Oct 23, 2013 at 1:43 PM, Dick Hollenbeck <[email protected]> >> > wrote: >> >>> >> >>>> >> >>>> # line 129, 151, 159 >> >>>> sudo rm -rf build && mkdir build && cd build >> >>> >> >>> sudo was missing on 3 lines, got that. (A patch would make this >> >>> clearer.) >> >>> >> >>> But I refuse to have the user building in a protected directory. sudo >> >>> should not be >> >>> necessary to remove the build directory, so there is something else >> >>> wrong here. >> >>> I am rejecting this until we can get a better handle on this problem. >> >> >> >> >> >> Fabrizio, >> >> >> >> Where are we creating the build directory? >> >> >> >> That's the bug. >> >> >> >> So we have a partial fix committed, and need to work through the build >> >> directory location, >> >> and creation. >> >> >> >> >> >> Dick >> >> >> >> >> >> _______________________________________________ >> >> 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 > > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
