excellent for the first time in those 2 years someone that did there hoework. this is my 2 cents.
first as for /usr/local and /opt install it there, fink allows that. but after you install into say ./usr/local, do a fink install sdl then install OSXMplayer....crap that just broke fink and you don't know why....oh darn, but it was a better place wasn't it the reason OSs like FreeBSD can install into /usr/local is they don't have .pkg and other native ports using none native installed libs being installed on it to muck everything up. /sw if a great choice as nothing uses it, /opt/fink is equally good but /opt is used so there is an very small risk none the less a bigger risk then /sw, and really what does it matter so much, the software builds ad installs find no matter where and runs great, and in /sw it's easy to mv it to a new volume and symlink it to continue and not lose any info and it's easy to nuke fink and not have to reinstall OSX. try that on FreeBSD. My solution is this....if you don't like /sw then don't install fink there, /sw is just the recommended install and the binary location. It's not required. [EMAIL PROTECTED] writes: >OK, here's my problem with /usr/local/fink: > >If you read the section of the Filesystem Hierarchy Standard >(http://www.pathname.com/fhs/2.2/fhs-4.9.html) about /usr/local, it >describes it for use by the system administrator to install software >locally. I always look at FreeBSD as an example of this. Pretty much >anything you install in FBSD via the ports system goes into the /usr/local >hierarchy. However, it's not usually broken down by a specific package, >but >the individual packages are alongside each other in the directories. So, >if >I port bash, parts of it go in /usr/local/bin, others in say >/usr/local/man, >etc. I feel that if Fink is going to use the /usr/local structure, it >should >be managing the whole structure and not a selfnamed subfolder. > >Now, bearing that in mind, I think that /opt/fink is better suited: > >http://www.pathname.com/fhs/2.2/fhs-3.12.html > >"/opt is reserved for the installation of add-on application software >packages. > >"A package to be installed in /opt must locate its static files in a >separate /opt/<package> directory tree, where <package> is a name that >describes the software package." > > >So, to summarize, if you're using the /usr/local structure, you should be >installing your static files in the appropriate folders within that >structure (/usr/local/bin, /usr/local/lib, etc), not within a self named >subfolder for all of your files; that is what /opt is for. Though that's >according to the FHS, which not a whole lot of Unices adhere to. /opt/fink >makes a lot more sense to me than /sw/fink. Also, since /opt is hidden by >default, you don't run into the confusion/problems of having the /sw >directory suddenly starting appearing when you are in the Finder (I >personally use SetFile -a V to hide it, I like a nice clean look). My >vote i >s for /opt/fink. -=[JFH] Justin F. Hallett <Systems Analyst> -=[JFH] Rendek Communications Inc. -=[JFH] [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
