2009/5/14 kevin beckford <[email protected]>: >> > I think the best course of action would be to make a Ports file for >> > cherokee >> > as macports is pretty standard for mac developers. > > This is definitely the way to go. Using macports would allow integration > with the rest of the dev tools. I personally prefer macports over ad hoc > mixtures of packages. There is a whole ecosystem for compiled free software > via macports with updates and easy sync'ing via 'port sync && port upgrade > outdated'
All right! I guess you're right.. the chance to easily update the software is worth the trouble. > My vote would be to make a cherokee port _first_ and then maybe fool around > with the package. Hell, upon reading the ports manpage I see you can : > "PACKAGING TARGETS > There are also targets for producing installable packages of ports: > pkg > Creates an OS X installer package of portname. > mpkg > Creates an OS X installer metapackage of portname and its dependencies. > dmg > Creates an internet-enabled disk image containing an OS X package of > portname." > do things like the above.... > Ports! I say use them! ;) Nice to know that.. I guess I'll be creating the .pkg in the meantime and perhaps it could be better to no binaries for a while. This is the first piece of advise I got from StackOverflow.. makes sense to me: "Do not install it directly in /usr. That's Apple's domain. Though /opt might be okay, it will not be in the default path and is not commonly used as a default installation location for third-party Unix software in Mac OS X. My advice is to install everything under /usr/local. Apple will not touch this area (e.g., during system updates, etc.), /usr/local/bin should be in the default path for users, and I have observed many other Mac OS X server software packages using this location. Most Mac OS X packages I've used (and most software I've built from source on Mac OS X) will create a /usr/local/whatever/... containing directory, however. So, for example, all of MySQL would be under /usr/local/mysql/... That means the MySQL binaries are in /usr/local/mysql/bin/... which is not in the default path for users. But I think the improved isolation of that extra level of directory structure is worth this sacrifice. (Another option is to install everything under /usr/local/whatever/... but then add symlinks to your most important executable(s) under /usr/local/bin)" For the package thing I'm buying into installing to /usr/local/cherokee and have a post install script make all the proper symlinks so binaries and manpages end up working out of the box. Antonio Lima-Perú _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
