I already addressed this in the second email I sent to the list on this topic.  
You can't sim-link to a file that is already present, you'll need to rename the 
original file first, then you can sim-link the newer version to the makeinfo 
filename.  
I've never used homebrew, but if it doesn't run as root, you won't be able to 
use it to overwrite a program in the /usr/bin folder, because you don't own the 
file, and root has higher privileges than you do, so perhaps if you precede the 
homebrew command with a sudo command, it might work for you.

But, just for reference, this is why I don't use any package tools such as 
homebrew or macports to do things for me, because I never know exactly what it 
is they're trying to do to my machine.  If I download, compile and install the 
programs myself, I know exactly what's going on every step of the way.

<--- Mac Access At Mac Access Dot Net --->

To reply to this post, please address your message to mac-access@mac-access.net

You can find an archive of all messages posted    to the Mac-Access forum at 
the list's public Mail Archive:
<http://www.mail-archive.com/mac-access@mac-access.net/>.
Subscribe to the list's RSS feed from:
<http://www.mail-archive.com/mac-access@mac-access.net/maillist.xml>

As the Mac Access Dot Net administrators, we always strive to ensure that the 
Mac-Access E-Mal list remains malware, spyware, Trojan, virus and worm-free.  
However, this should in no way replace your own security strategy.  We assume 
neither liability nor responsibility should something unpredictable happen.

Please remember to update your membership preferences periodically by visiting 
the list website at:
<http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>

Reply via email to