Installer should allow installation of macport in custom locations - for users without admin access

Anders F Björklund afb at macports.org
Fri Jul 30 02:40:00 PDT 2010


Jeremy Lavergne wrote:

>> I think MacPort is mainly for user programs and libraries.  Admin  
>> tools such as daemons and OS maintenance (such as stuff in /bin  
>> and /sbin)  should have already been in the OS X itself rather  
>> than in
>> MacPort.
>
> The packages in the `aqua` category are the only ones in MacPorts  
> that meet the .app qualifications. Not surprisingly, they're  
> installed into the /Applications folder by default.

Actually, that *is* rather surprising. The logical place would be to  
have them in ${prefix}/Applications, just like the frameworks were  
changed to use ${prefix}/Library (rather than /Library). But it was  
something hardcoded in the OS that made the subdirectory / 
Applications/MacPorts a better default... (and no idea why it  
couldn't just be a symlink)

It would be better/easier to have everything under ${prefix}, instead  
of installed into 4 possibly different locations (prefix, tclpackage,  
applications, frameworks). Ignoring system ports that actually need  
to install things elsewhere, that is (startup scripts, kernel  
modules, etc). That way, you would only have one toplevel folder to  
deal with...

--anders



More information about the macports-dev mailing list