On Tue, Aug 10, 2010 at 8:48 PM, CVBruce <cvbr...@gmail.com> wrote: > As part of the Mac OS X install I have to create a shell script to put > the symbolic links into /usr/bin etc. > > The installer executes the script after the install. The script has > version, release and mod numbers in it.
This is essentially the way the deb and rpm packages / make targets work. > I created an input script, postflight.in and added the necessary sed > commands to the Makefile.am to tailor the script to the current > environment. The problem is that where I put it in the Makefile it > gets executed in the 'make install' phase. The problem with that is > that usually 'make install' is usually executed as 'sudo make install' > and the resulting shell script ends up being owned by root. Not > exactly a good idea in my book, having an executable script owned by > root. You could look at how the deb: target in Makefile.am is set up. It is similiar to what you are doing. I'm not sure I understand the problem with the shell script being owned by root. If someone chooses to build as root, then I would expect that the script would be owned by root. If they choose to not build as root, then the script would not be owned by root. If, on the Mac, they *have* to build as root, then it seems like it would expected that the script be owned by root. You can write up the instructions on how to build the Mac package. You could allways make the Mac packaging step a separate target from building the interpreter. I.e., your instructions could be: ./configure --disable-static make make macosx_package #or whatever name you want If you want the stuff that creates the script separate from building the interpreter, put it in a separate target. Oh, I just reread what you said, about it being in "make install." I would think that you would want a separate target that makes the Mac installation *package*, and not have any of it in make install. Again, I think the rpm and the deb targets might be something you could model this on. -- Mark Miesfeld ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
