I have always used /usr/src, now with the Mac the way it is, I use /usr/local/src.
On Mon, 04 Sep 2017 16:05:42 -0400, Cheryl Homiak wrote: > > After looking over the post I did about compiling screen and brltty, I > realize I made a large assumption I should not have made - but then when one > makes assumptions, by default one isn't seeing other possibilities. > > I do not usually compile in the home directory even on the Mac, which by > default does not have a /usr/local/src, I create one and have all of my > downloaded sources and git and svn downloads there as well. This probably is > not best practice but was actually what people I learned from seemed to be > doing when I was learning. > > Because of this assumption, I assumed that when the screen source was > downloaded and when the git folder for brltty was done, the downloads would > be moved somewhere outside the home directory (on the Mac they probably > shouldn't just be worked on in Downloads) and git and svn would be run > outside the home directory. For that reason I thought John would put his > sources in /opt/local where he was placing brltty and screen. But obviously > just because a program is going to be installed in that directory doesn't > mean it needs to be moved there and compiled there; even when I install > brltty with the defaults I still run from /usr/local not from the directory > where brltty is going to end up installing. > > So I should not have made this assumption. Therefore I should perhaps have > given instructions to unpack the source in the home directory or maybe to > create a directory such as src in the home directory that would contain > source and svn and git downloads. It is true that if this is done sudo is not > needed until the make install stage is reached. So if somebody else wants to > redo this, that is fine of course but otherwise when I have time, I will do > so. Because I automatically always used /usr/local/src as my base for > compiling and installing, I really had not thought through this issue. > > The one question I have is: Should I just instruct to unpack in the home > directory or should I advise that a directory should be made within the home > directory for compiling and managing svn, git and other source downloads? I > actually think I may change my own practice now that I realize what my > assumptions were. > > -- > Cheryl > > May the words of my mouth > and the meditation of my heart > be acceptable to You, Lord, > my rock and my Redeemer. > (Psalm 19:14 HCSB) > > > > > On Sep 4, 2017, at 11:19 AM, Cheryl Homiak <[email protected]> wrote: > > I primarily wrote this for one person. Dave and you and whomever wants to be > involved may certainly edit it as they wish. Your point is understood. > > -- > Cheryl > > May the words of my mouth > and the meditation of my heart > be acceptable to You, Lord, > my rock and my Redeemer. > (Psalm 19:14 HCSB) > > > > > On Sep 4, 2017, at 10:47 AM, Nicolas Pitre <[email protected]> wrote: > > On Sun, 3 Sep 2017, Cheryl Homiak wrote: > > > Actually this is not true in the Mac unless you do everything in your > > home directory. This is if you are compiling. But probably the sudo > > was not needed in the ls command. > > It is highly recommended that you compile things in a subdirectory of > your home directory. The point is to do as much as possible without root > privileges. Any issues, e.g. bugs with the Makefile than ends up > deleting files from / would have less of an impact on your system that > way. > > Of course on your own system you may do as you wish. But in a guideline > document that inexperienced people will rely upon I think it is > important to stick to best practices. > > > Nicolas > > > _______________________________________________ > This message was sent via the BRLTTY mailing list. > To post a message, send an e-mail to: [email protected] > For general information, go to: http://brltty.com/mailman/listinfo/brltty -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici [email protected] _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.com/mailman/listinfo/brltty
