Mat Caughron <[EMAIL PROTECTED]> wrote: [snip] > So here are my suggestions on how to make things work together well: > http://www.macgimp.org/fink
Mat, if I can summarize your proposal in one sentence, you propose to use PackageMaker to install an /sw directory (via pax) which would contain "only files... that the Fink gimp package itself would write." Let's examine the effect of this proposal on users under various circumstances. 1) A user already has a fink installation in /sw. His or her fink installation is now modified by your installer. Because the dpkg/apt-get system has not been used to do the modification, further fink updates or additions are likely to run into trouble. 2) A user begins with your installer. Later the user wants to install or update other packages via fink. This will only work if your installer provides a working dpkg system with an accurate set of debian logs, corresponding to the files that were installed. 3) A user has installed a previous version of macgimp using your installer, and now has a new version of your installer. What happens during an upgrade? Are obsolete files cleaned out, as well as new ones being put in? 4) A user has a fink installation with some functionality provided by symbolic links. (This is my personal situation; I ran out of room in one disk partition so I moved /sw/fink to another partition and put in a symbolic link.) Because pax blasts through symbolic links, using your installer destroys the user's setup. OK, so what kind of alternative would I propose? A) Make a fink installation, with all the packages your heart desires, in a directory /macgimp rather than /sw, and package it with PackageMaker. It is easy to change the default fink directory during installation. (Please be sure to give the fink project credit for creating all the stuff that goes into this directory!) This way, your installation will not interfere with an installed or future fink installation. or, B) Write a small Mac OS X app which will serve as the installer you want. It can install a working fink system, and then run a script which would let apt-get install the gimp-related debian files (which would also be included on the .dmg you create). This method could only be used to install afresh, not to update a pre-existing system. However, a more sophisticated script could be imagined which would test for the presence of fink, etc etc. and do the right upgrade thing. In either case, though, there is a fundamental problem of getting the user to include the correct thing in a .cshrc or .tcshrc file. How do you handle that? -- Dave _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
