26 | | |
27 | | === I just installed MacPorts 1.2 from the .dmg and I seem to have lost all my installed ports (aka Cisco VPN ate my MacPorts!) === |
28 | | |
29 | | '''This issue has been resolved in 4.9. The VPN client installs itself in `/private/opt`''' |
30 | | |
31 | | When you install the latest CiscoVPN Client it copies all the files in `/opt` to `private/opt`, deletes the files in `/opt` and replaces them with a link from `/opt` to `/private/opt` (and taking a long while to do it). The MacPorts .dmg installer overwrites this link and leaves the `/private/opt/local` no longer "connected" to MacPorts. (If you wondered why it took Cisco VPN 4.7 forever to install, this would be the answer, BTW.) |
32 | | |
33 | | One possibility is to rename the newly installed `/opt` to `/opt2` (and later delete it) and then move `/private/opt` to `/opt` and then reinstall MacPorts 1.2 from the .dmg. |
34 | | |
35 | | Another possibility is to munge the dumbass Cisco VPN installer preprocessing script to '''not do that''' before you install Cisco VPN. You then need to modify one other file after the Cisco installation so that it can find a command line tool it's looking for. Unfortunately, I'm now fuzzy on the exact details. |
36 | | |
37 | | Best of all worlds is to avoid using Cisco VPN. With Cisco's keenly brilliant engineering power amply demonstrated in their installer scripts, do you really want them running a kernel extension, fer crissake? |
38 | | |
39 | | {{{ |
40 | | $ ls -l /op* |
41 | | lrwxr-xr-x 1 root admin 12 Dec 5 12:44 /opt -> /private/opt |
42 | | $ sudo mv /opt /opt2 |
43 | | $ sudo mv /private/opt /opt |
44 | | $ ls -l /op* |
45 | | total 0 |
46 | | drwxr-xr-x 3 root wheel 102 Nov 17 23:46 cisco-vpnclient |
47 | | drwxr-xr-x 13 root wheel 442 Dec 5 19:56 local |
48 | | }}} |