[Xquartz-dev] Re: X11.pkg
merlereinhart at mac.com
Sun Dec 2 07:42:45 PST 2007
I'm still seeing some incorrect ownerships on the updated files.
A philosophical question: Since it appears that only some of the files
are changing compared to the standard Leopard X11, do we want to include
only those that have changed, or an entire complete/self-contained X11
install? I don't think I have a preference either way.
Here a non-philosophical question: Will this work to overwrite the X11
install for those that down-revved to Tiger's X11? Or should the
detect that and deal with it in a pre-install script? Or should it
it and ask that Leopard's X11 be installed first to cleanup?
I don't have any way to test this situation.
The ownership on the following files should be root:admin (0/80) not
The ownership of the following file should be root:wheel (0/0) not
You can change these in a couple of ways:
1) do a chown on the files you are including in the package
2) In the 'Contents' pane when the included folders are highlighted,
set the individual ownerships of the files that are wrong.
(I don't think you have to set the 'Overwrite Directory
for this to be effective).
You can double-check things are right after you've built the package
the following command:
lsbom `pkgutil --bom <package_file>`
The output will be a lot of lines with each showing
filename, permission bits in octal, UID/GID, file size, 32-bit CRC
If it's a symbolic link, you see the link target after the checksum.
Finally, it looks to me like the postinstall script is firing.
on the final /usr/X11/bin/Xquartz file shows the resource fork is there.
As a side note, Rez only gets installed if the Xcode Developer Tools
If they're not installed, then I would expect Installer to throw an
running the postinstall script. This might be the cause of the error
one person saw. Should we look for the Developer Tools in the Install
abort with a good error message if they are not present before
Another way around that would be for you to include the resource fork
prior to building the package. As long as the 'Discard Resource
Forks' is not
checked in the Package Flags, that should work.
On Dec 2, 2007, at 1:58 AM, Jeremy Huddleston wrote:
> Ok, I have a new version up that should take care of all it issues
> The only thing I'm not sure about is the postinst script. I'm not
> sure that it's being done correctly. Can someone tell me how to
> verify if the postinst script is being run? It should be doing:
> /bin/launchctl load -w /System/Library/LaunchAgents/
> /usr/bin/Rez -a -o /usr/X11/bin/Xquartz AddPlist.r
> with AddPlist.r and Xquartz.plist in the scripts directory.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2425 bytes
Desc: not available
Url : http://lists.macosforge.org/pipermail/xquartz-dev/attachments/20071202/1aa9d50f/smime-0001.bin
More information about the Xquartz-dev