On Jan 13,2003 08:03:38 -0600, Jared <[EMAIL PROTECTED]> wrote : >Thanks for the reply. > >On Monday, January 13, 2003, at 07:37 AM, David R. Morrison wrote: > >> However, I *implore* you not to do this if you have built the Fink >> packages >> using the default /sw installation location. > >I assure you, I have no intention of modifying the /sw directory. All >my testing was done by copying files FROM /sw on one computer to /usr >on another computer without Fink. The program I am packaging up worked >normally using this method. I am planning to install the needed files >into /usr/lib and /usr/include. >
Libraries such as libxml2 won't work if you copy them to a different location. When the library is compiled, the path name at which it will be installed is written into the actual library itself. This same path name is then written into any binaries which were linked against that library. This is why I suggested you would need to compile with a different Fink prefix. >> What you could do instead, is to pick an installation prefix of your >> own >> (let's say /opt/jared), and run the Fink bootstrap with the choice of >> /opt/jared as installation prefix. Then you can compile the Fink >> packages >> you need, bundle everything up into a .pkg, and distribute them to >> your heart's content. > >This seems reasonable. However, if I am going to add my own prefix, I >would probably put it inside /usr or something. I don't want my >directory of a dozen files sitting at the root of someone's computer. >I'd rather have it all nicely tucked away somewhere. That's why I'm >planning just to integrate it into /usr. If I do add my own prefix, I >will probably need more assistance from you guys because I don't know >how to do the bootstrap thing you mention. Hopefully I won't have to go >that route. > >Can anyone tell my why I shouldn't copy files into the /usr directory? > /usr itself should be reserved for use by the operating system. The next time Apple updates your system, things placed directly into /usr might get wiped out or modified. One standard location to put things is /usr/local, i.e., /usr/local/bin, /usr/local/lib. However, because lots of people install things there, there is some danger that your installation will get wiped out by something else the user instals. >One more question. I am having difficulty finding good information >about PackageMaker. I can't figure out how to install more than one >file to different locations. For example, my libxml2 package will have >to install some files into /usr/lib and some files into /usr/include >and one file into /usr/bin. Any idea how to do that? > My understanding is that PackageMaker can only install things into a single tree, whose "root" (= starting point) can either be predetermined by you or selected by the user. Since you want things to go into a predetermined location, you'll make that choice. You will need to create a tarball which will get installed into /usr (or wherever you choose) and has subdirectories like lib, include, and bin. -- Dave ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
