So I think the best way is to do away with the installer and put the entire macport (base, ports and configuration files) within MacPort.app.
All the user needs to do is to include the bin path(s) within MacPort.app in .bashrc Then whenever we run "port install", port will detect the directory of its MacPort.app (a machine can have multiple copies of MacPort.app across the system) directory and install the ports correctly into its own MacPort.app Does this idea sound better? Mark On Thu, Jul 29, 2010 at 5:27 PM, Scott Haneda <[email protected]> wrote: > On Jul 28, 2010, at 10:07 PM, Scott Webster wrote: > >> I guess Mark is presumably thinking of a situation where someone just >> doesn't have the permissions to install in /opt/local so it isn't just >> a willy-nilly desire to put it somewhere else, but still it seems that >> compiling from source is not all that hard. > > Would it be possible to `ln -s /opt/local ~/opt/local` and work around this > entirely with the normal installer? > -- > Scott (* For off-list contact, replace talklists@ with scott@ *) > > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
