sorting out trace mode "access denied" messages

[Allen McBride]

Thanks for the hints.  I changed the subject line to be more  
descriptive.

Two things:

First, I added the line "configure.env PYTHON=${prefix}/bin/python2.5"  
to my portfile.  And now when I do a "sudo port -v configure", I see  
configure is clearly finding python2.5, not python.
Yet, now when I do "sudo port -t destroot", I get the following two  
lines repeated 14 times:
trace: access denied to /opt/local/Library/Frameworks/Python.framework/ 
Versions/2.5/lib/python2.5/os.py (*unknown*)
trace: access denied to /opt/local/Library/Frameworks/Python.framework/ 
Versions/2.5/lib/python2.5/os.pyc (*unknown*)
But "port provides" says these two files are provided by python25.

Second... and I don't know if this is important, but...
"port provides /opt/local/bin/python", for me, returns "/opt/local/bin/ 
python is not provided by a MacPorts port."
Yet /opt/local/bin/python, which is a symlink to python2.5, was  
definitely created by python_select (I ran python_select again just to  
be sure).
And "port provides" does confirm that "python_select" is provided by  
python_select and python2.5 is provided by python25.

As always, though, "sudo port install" still works fine.

Thanks,
Allen




On Mar 16, 2009, at 2:31 PM, Daniel J. Luke wrote:

> you can do 'port provides foo' to find out what port provides foo:
>
> % port provides /opt/local/bin/python
> /opt/local/bin/python is provided by: python_select
>
> If you can tell the configure script to use ${prefix}/python2.5  
> instead of ${prefix}/python, that would be good.
>
>> So, I'm thinking I can go ahead and submit my Portfile to MacPorts  
>> despite these "access denied" messages from trace mode.  Any  
>> suggestions to the contrary?
>>
>> Also, a question about the "maintainer" field of the Portfile...  
>> since I don't have commit privileges, I assume I should leave this  
>> as "nomaintainer" rather than putting my own e-mail in, correct?
>
>
> No, you can put your own email address in the field. For a little  
> while you'll need to bug a committer to actually commit any changes  
> to your port, but after you've done it for a while you should apply  
> for commit access so you can update it yourself.
>
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+
>
>
>