> On Jan 19, 2015, at 4:14 PM, René J.V. Bertin <rjvber...@gmail.com> wrote:
>> One needs to set portdbpath in macports.conf to the 'real' path
> 
> Oh? I haven't, and I also don't see why it'd be required.

I was thinking of https://trac.macports.org/ticket/39850

> There has been a time where this kind of configuration obliged one to 
> deactivate sandboxing (trac #39850), but that issue has been solved.

well, as mentioned in #39850 setting portdbpath let you run with a symlink 
without deactivating sandboxing.

... but you're right, cal fixed it and it's been released (I though the fix was 
sitting on trunk still, but it made Macports 2.3.0)

--
Daniel J. Luke                                                                  
 
+========================================================+                      
  
| *---------------- dl...@geeklair.net ----------------* |                      
    
| *-------------- http://www.geeklair.net -------------* |                      
    
+========================================================+                      
  
|   Opinions expressed are mine and do not necessarily   |                      
    
|          reflect the opinions of my employer.          |                      
    
+========================================================+



_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to