Apache OpenOffice (AOO) Bugzilla – Issue 56189
modify Mac OS X packing
Last modified: 2006-03-26 15:16:22 UTC
For 2.0, we have used create-package.sh (in located solenv/unxmacxp/bin ) to create .dmg on Mac OS X. This method is wrong because simply bypassing all install and postinstall scripts. This way, some symlinks are missing (python-core-2.3.4 and python-core ...) and other actions are missing. This issue is created to fix this for 2.0.1 and future versions.
Created attachment 30593 [details] first version of a patch avoiding postinstall scripts for pyuno
The patch moves the symlink into the package, where they belong. The previous problem was that scp2 does not allow symlinks to directories, which now is handled in the epmtail_pyuno.txt file. With this first patch the execute permissions of python-core-xxx/bin/python don't get set. The plan to fix this is to use the new scp2 functionality to preserve the attributes of files contained in a zip archive. I need to figure out when this feature is available and whether we need to modify scp2/source/python/* for this.
obr: you are working on it, so it should be assigned to you, no?
The 'chmod +x' can be fixed as soon as CWS sdkinstaller is integrated.
add cc
Reading the Apple documentation on Software Distribution, I stumbled over the following limitation of Drag-and-Drop Installations: <quote> Drag-and-Drop Installation [..] One complication of using drag-and-drop installation is that it does not automatically support updating of prebinding. Prebinding is a process that can improve the user experience by providing a faster application launch. For more information on working with prebinding, see “Prebindingâ€. </quote> This makes me think the a "dmg containing a meta-package" approach might indeed by more appropriate - even though I am a big fan of the drag-and-drop installation. Any other thoughts ?
>This method is wrong because simply bypassing all install and postinstall scripts. partially wrong. we use portable as package method, so install/postinstall scripts are ignored. go back to osx, it should work.
maho: no no, portable is OK. What is wrong is the usage of portable packages. portable is tar archive *and* postinstall scripts. But the create-package.sh script does this: #install the packages to the temporary folder cd ${DESTDIR} rm -rf ${INSTALLTEMPDIR} mkdir -p ${INSTALLTEMPDIR} for Package in `ls $DESTDIR/$PACKDIR/*sw`; do echo "Installing ${Package}" tar -C "${INSTALLTEMPDIR}" -xf ${Package} done So it "installs" package. But it is not installing the portable package, it is unpacking one part of it, the tarball.
Accepting for 2.0.2.
obr: any news?
paveljanik: the python problem has been fixed by #i56955#, which makes reworking the create-packages.sh solution less urgent => adjusting the target.
obr, pjanik: In my humble opinion, this issue has been overtaken by 63030/63630 which are to go back to the installer vice a drag n drop fix James
James: I think the OOo packaging should support both formats, drag-and-drop and the OS X installer. However, since one outcome of the installer discussion was that if a product needs install time scripting, it should not be packaged as drag-and-drop installation, I am closing this issue as WONTFIX as you suggested.
.