tank wrote:
Everyone, I installed it last night and couldn't get it to work. I figured it was not going to work because in the instructions it says to copy the ypops and ypops.bin to the /usr/local/bin directory and I do not have that directory. I have a /usr/bin directory. I think the /usr/local directory was empty, so I tried it in the /usr/bin directory and after I installed it and tried to run ypops for the first time, apparently it tried to find the ypops.bin in the /usr/local/bin directory which did not exist. I think I am running 10.3.2, which I assumed would have the same directory structure as 10.3.5, which it worked on for Q3Q(right?)
Anyway, I thought I could maybe create a bin directory in /usr/local, but I couldn't remeber the unix command to do it, and I decided that it might look for some libraries in the same path, which would obviously not be there. As you can tell, I know very little about Unix, so any help would be greatly appreciated. I noticed that when I opened Terminal it uses Bash(if that matters).
This would be a great thing for all of the OSX users out there to get POP access to their Yahoo mail. As Q3Q said, let's use our collective brain power.
tank,
sorry for jumping in late. I was away to beat a deadline.
About the missing /usr/local/bin directory:
I was not aware that this is not part of standard Mac OS X file tree structure. Mine got created probably when I installed something previously. Anyway, the following is the command in a terminal window to create them: assuming you have the parent directory /usr/local. If not, follow the principle and create the parent first.
- Code: Select all
cd /usr/local
sudo mkdir bin
The first command 'cd' is change directory. It will place us at the specified directory. The second command 'sudo' is to execute the following command in administrator privilege. Because we are going to create a sub-directory in /usr, which is protected, we need it. The command 'mkdir' is make directory. Hopefully, you can place ypops and ypops.bin there.
Of course, the way you did (placing the files in /usr/bin) is fine, too. However, that directory will be modified when Mac OS X do system upgrade. Our customly built programs may get wiped out if they are placed there. The error message you had ('cannot fine ypops.bin') is due to the setting inside the file ypops. This file, acting as our launching agent, is itself a shell script. You can open it with a text editor. You will see that it calls ypops.bin by specifying the absolute directory path name: /usr/local/bin/ypops.bin. If you want to stick with this place /usr/bin, you simply edit that line to reflect the new location. That should do.
Now, you will probably encounter the following problem.
About the missing preference file (ypopsrc)
pacifier1er,
Obviously, your Mac has /usr/local/bin directory. You don't have problem like tank's. However, ypops in your Mac asks the preference file ypopsrc to be at /Users/pp location. Surprise! That user name is mine. I need to check why ypops has the location for ypopsrc hard-coded. I mentioned somethign similar in another thread ('ypcompile need help') about my first impression after compilation. I said that ypops insists the preference file to be placed at hoem directory, even though I specified it to be /usr/local/share as suggested in ypcompile shell script. I am going to check if I accidently specify my home directory for it by compiling it again. If it is simply because my ignorance during the compilation, the new compilation should fix it. On the other hand, if it is a bug in the program, then I don't have a fix. We will see.
About 'no .bin' file in your compilation
pacifier1er,
judging from the naming convention of the preference file '.yahoopops', and the way the compiled binary being located '/Users/ian/unix/yahoopops', I guess your compilation is of the version 0.3.9. Granted, that is the one listed in yahoopops source forge download/Mac section. However, the one we are discussing has the version number 0.6. It's final (not beta) version, and is pointed by in a recent post of the developter member, but not in the download/Mac area.
For now
The installation process should have been smoothier. My apology. I will modify the instruction (included in the zip) to include the scenario tank encountered in which the expected places to store the files do not exist. In addition, I will maybe write a shell script to handle making directory, copying files.
Also, the problem of the hard-coded path for the preference file is troubling me. I will investigate if it is due to my ignorance during the compilation.
Thanks for the feedback.