/Stefan

On Thu, Aug 5, 2010 at 10:10 PM, Hans Aberg <haberg-1@telia.com> wrote:

On 5 Aug 2010, at 21:52, Stefan Blixt wrote:

I run chuck from the command line without having followed those instructions - I didn't do any of that dangerous sudo stuff, I just added the place where I put the chuck binary in my path by editing .profile.

Even that might be too complicated to those that do not know about Unix stuff. But one can put in the directory where the file is, and run it using './chuck <file>'. On a Mac, one can put it into /Applications/ and run it with /Applications/chuck.

But I suspect that some things won't work properly without root permissions - probably Internet stuff.

Having said that, it's definitely not an easier way to do it. Couldn't there have been a better installer for chuck that does all of this automatically, just requiring the user to enter a password at the proper time? Saying "enter password" instead of "now we're going to modify your terminal" feels more... diplomatic.

That would be better.

It's curious, I've gotten so used to roaming around unix systems, doing all kinds of crazy stuff. It's good to be reminded now and then that opening .profile with vi (.profile isn't visible in Finder), and adding stuff to the PATH variable isn't a very obvious thing to do.

Fink also adds a line to .profile, if it is not already in the search path.

Thinking about how MacOS got slammed on top of FreeBSD still cracks me up.

That was how it began, but now it is certified UNIX. BSD is not. So it has departed considerably.

Perfectly logical, but oh how confusing when you come from a Unix background.

What is confusing?

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

--
Release me, insect, or I will destroy the Cosmos!