selfupdate failing under Leopard

Ryan Schmidt ryandesign at macports.org
Fri Nov 16 14:27:56 PST 2007


On Nov 16, 2007, at 15:57, James Berry wrote:

> On Nov 16, 2007, at 12:05 PM, Daniel J. Luke wrote:
>
>> On Nov 16, 2007, at 2:59 PM, markd at macports.org wrote:
>
>>> I agree.  Especially since the woes of manually installed OSS is  
>>> one if
>>> the problems MacPorts is trying to overcome.  :)
>>>
>>> Is readline the main offender?  I want to document this problem  
>>> and though
>>> I think any non-MP software could potentially be a problem, I might
>>> mention the worst offenders as examples.  What are others?
>>
>> It's certainly the one I've seen people talk about most often.
>
> The use-case for readline in macports is quite small. I'm inclined  
> to simply disable readline by default, which would eliminate this  
> problem. All opposed?

That might eliminate the problem of selfupdate not working in  
relation to the rogue readline in /usr/local, but it would not fix,  
for example, ticket 12040, in which db44 fails in weird ways if a  
rogue readline is present. I believe other ports can fail in these  
ways as well.

http://trac.macports.org/projects/macports/ticket/12040

I would prefer a solution that causes MacPorts to scream and shout if  
a readline is present in /usr/local.



More information about the macports-users mailing list