packagemaker vs symlinks?
packagemaker vs symlinks?
- Subject: packagemaker vs symlinks?
- From: Greg Neagle <email@hidden>
- Date: Thu, 4 Jun 2009 13:44:42 -0700
Are there known issues with the command-line packagemaker (3.0.3) and
symlinks in the package root?
When I try to build a package that installs some symlinks that point
to places out on our organization's NFS mounts, sits forever at the
Preverifying step:
root# /Developer/usr/bin/packagemaker --root /var/folders/zz/
zzzivhrRnAmviuee+++F7E++2GI/-Tmp-/tmpkDyZpN/Leopard_DA_NFS_additions --
id com.disneyanimation.Leopard_DA_NFS_additions --no-recommend --out /
Users/Shared/pkgs/Leopard_DA_NFS_additions.pkg --verbose
2009-06-04 10:53:22.978 packagemaker[31581:807] Setting to : 0 (null)
2009-06-04 10:53:22.980 packagemaker[31581:807] Setting to : 0 (null)
2009-06-04 10:53:22.982 packagemaker[31581:807] relocate: (null) 0
Preverifying Leopard_DA_NFS_additions
Preverifying Leopard_DA_NFS_additions
Checking bundle identifiers
Checking package configuration
Checking contents
Loading contents
Eventually I grow impatient and control-C it.
If I clear out the symlinks in the packageroot and then build, it
builds fine, but completely misses the point. Is packagemaker
traversing the symlinks in the packageroot? I don't see a --no-follow
type option in packagemaker's command-line options.
-Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden