Leopard status

[Rob MacLeod]

On Dec 29, 2007, at 1:04 PM, Ryan Schmidt wrote:

> On Dec 29, 2007, at 08:28, Rob MacLeod wrote:
>
>> OK, I found the Leopard patch, managed to install the patch  
>> (instructions on this process could use some expansion and  
>> updating), and the build seemed to work:
>
> Which patch are you talking about? Is it attached to a ticket? Which  
> ticket?

# 13294

>
>
>> [airfriday:~]$ sudo port -v install emacs
>> --->  Installing emacs 22.1_1
>> --->  Activating emacs 22.1_1
>> --->  Cleaning emacs
>> --->  Removing build directory for emacs
>>
>> However, the emacs binary did not end up in the /opt/local/bin,  
>> even though it does exist in
>> /opt/local/var/macports/software/emacs/22.1_1/usr/local/bin
>
> Apparently it has ended up in /usr/local/bin instead of /opt/local/ 
> bin. Assuming your MacPorts prefix is /opt/local as per usual, this  
> is an error. Without knowing what patch you're talking about, I  
> don't know yet whether this is a fault in the patch or an unrelated  
> issue.

Thanks,

Rob

>
>
>> Is there some final magic I need to do in order to get things in  
>> their rightful place.  Obviously, I can copy manually but I assumed  
>> the install script should take care of this sort of detail?
>
> Yes, MacPorts should take care of installing things in the right  
> place for you. If it does not, it is a bug.
>
>> On another note, if there has been a patch available for emacs for  
>> a month now, why is it not part of the current install? I mean, why  
>> should it still be necessary to apply the patch this long after it  
>> is in place?
>
> Presumably because the maintainer of the emacs port has not gotten  
> around to testing the patch. Our policy is that if a maintainer does  
> not react to an issue within 72 hours, any other committer may do  
> so. I myself would not feel completely comfortable committing any  
> Leopard emacs bugfixes, since I don't have Leopard and I don't use  
> emacs. But hopefully someone else here meets at least one of those  
> criteria. If you'll tell us which ticket it is, hopefully someone  
> will have a look.
>
>> On Dec 28, 2007, at 9:47 AM, Ryan Schmidt wrote:
>>
>>> On Dec 28, 2007, at 09:36, Rob MacLeod wrote:
>>>
>>>> On Dec 28, 2007, at 8:31 AM, Ryan Schmidt wrote:
>>>>
>>>>> For each port you find that fails to install, please search the  
>>>>> issue tracker to see if it has already been reported. If it has,  
>>>>> check the ticket to see if there's a patch. If there is, try it  
>>>>> out. If it works for you, say so in the ticket so we'll know we  
>>>>> can commit the patch. If there's no patch but a workaround, that  
>>>>> might let you bypass the problem as well. If there's no ticket  
>>>>> filed, please file one.
>>>>
>>>> Thanks for this information but I am afraid I have to ask some  
>>>> more questions.
>>>>
>>>> How do I search the issue tracker? Each time I try and follow the  
>>>> link to any error reporting, it asks for a username and password  
>>>> that I have not received.
>>>
>>> You'll have to sign up for an account in the issue tracker if you  
>>> want to file new tickets or add comments to existing ones, but you  
>>> should be able to just search without logging in. Go to http://www.macports.org/ 
>>>  and click Support & Development in the left navigation. Then  
>>> click View Tickets in the top navigation. Then click Custom Query  
>>> over on the right. Then select Summary from the Add Filter menu.  
>>> Then type your search string into the text box and click Update.
>>>
>>> To register for an account or log into an existing one, click  
>>> Register or Log In at the top right of any issue tracker page.