Creating Alias' or symbolic links in Composer?

[ryanhollitz]

Hello-

I’m working on a Cisco VPN package. During the install it creates a symbolic link from /private/etc/CiscoSystemsVPNClient -> /etc/opt/cisco-vpnclient. When I make the package, it puts the contents of cisco-vpnclient in a directory called CiscoSystemsVPNClient and makes it a folder. This breaks the package when overriding the current users, but this content is need for VPN connections. I have tried to delete the CiscoSystemsVPNClient directory and then re-add the directory as an alias, but each time I search in the OS, the symbolic link is followed. I know that some how this is possible, as I have a package that was made for the previous version that has a Alias folder for CiscoSystemsVPNClient.

Any help would be greatly appreciated. :)

Thanks,
ryan

[donmontalvo]

Hi Ryan,

Just curious why you're repackaging the Cisco client? Cisco is one of those companies that I trust enough to deploy their packages.
Um...after I snapshoot the install so I can verify what it's doing. :)

Citrix is one of the (many) that I don't trust...

http://donmontalvo.com/citrix/citrix-pkg-from-hell.png

That said, there are still some issues with Composer...I use it, but I still find myself going back to Packagemaker/Iceberg at times.

Don

[ryanhollitz]

Hello All-

It turns out that I needed to go into the Application Support folder and
edit the file structure there to get the Alias to show up properly in
Composer.

I was using Composer so that I could also distribute our specific
configuration. It turns out that this works! I was able to get it to
install properly. The system requires the VPN subsystem to be restarted, or
the machine needs a reboot, but then it worked like a champ! :)

We would like to use the Snow Leopard built-in VPN, but haven't as of yet
figured out how to package those settings.

Thanks all,
ryan

[donmontalvo]

Hi Ryan,

We've run into issues with aliases vs symbolic links when packaging. Glad you were able to resolve things. :)

Don