#14326: macports on xserve cluster ------------------------------------------+--------------------------------- Reporter: pawel.matykiewicz@gmail.com | Owner: markd@macports.org Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: guide | Version: 1.6.0 Resolution: | Keywords: xserve cluster ------------------------------------------+--------------------------------- Changes (by jmpp@macports.org): * owner: macports-tickets@lists.macosforge.org => markd@macports.org * priority: High => Normal * component: base => guide Comment: We don't have a "cluster" specific configuration as such, but there certainly are ways in which MacPorts can be built in a more confined fashion so that it becomes share'able across a network through a single volume. Off the top of my head, you need to pass a custom `--with- tclpackage` flag to the configure script so that the `macports1.0` package also gets installed into your confined location, presumably within your installation `${prefix}`, and not onto the default `/Library/Tcl` path. Don't recall at the moment if there are other things that you need to relocate off their default paths to fully confine your MacPorts installation, so I'll assign this ticket to myself so that I can write something up for the guide or Wiki later for public consumption. -jmpp -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14326#comment:1> MacPorts </projects/macports> Ports system for Mac OS