1.7.0 beta: working great!

[Ryan Schmidt]

On Dec 7, 2008, at 10:40, Jay Levitt wrote:

> Ryan Schmidt wrote:
>> On Dec 6, 2008, at 20:24, Jay Levitt wrote:
>>> I usually have all sorts of bad luck with the TCL environment bug,
>> I'm sure everybody running MacPorts 1.6.0 on Leopard does.
>>> dependencies, etc.
>> What dependency problems do you mean?
>
> I'm not entirely sure, because I hadn't been paying attention until  
> the 1.7.0 train started rolling in.  I just have vague memories of  
> "can't install this thing".

Ok, if you encounter a problem again, be sure to report it right away  
with exact error messages and such so that we can look into it. :)

>>> I just did a port upgrade on all my outdated ports - about 8 or 9  
>>> of them, including ImageMagick, which is known for never building  
>>> easily -
>> What ImageMagick build problems are you talking about? I'm not  
>> aware of any.
>
> I used to build it from source all the time, and on every machine I  
> ever tried (whether Windows or Mac or Linux), there was some not- 
> quite-anticipated dependency on a system library that was the wrong  
> version but that autoconf thought was good, or something like  
> that.. this was a while ago.

A great reason to use MacPorts -- it handles dependencies correctly  
for you, and only one person (the maintainer -- me for ImageMagick)  
has to figure out the quirks of the software, so that everyone else  
gets to install it as easy as "sudo port install ImageMagick".

> Recently, I know I tried installing the latest ImageMagick with  
> MacPorts 1.6.0 on a Mac that already had a previous version, and I  
> remember an error about having to manually deactivate the one port  
> before activating the new one - an error I didn't get when I  
> upgraded with 1.7.0.

If you already had an older version of the ImageMagick port  
installed, and then typed "sudo port install ImageMagick" to get the  
new one, then MacPorts will at the end issue an error message that it  
cannot activate the new version because another version is already  
active. That's the correct behavior. To deal with it, you need to  
then deactivate (and, if you like, uninstall) the old version, then  
activate the new version. To avoid all this, instead of typing "sudo  
port install ImageMagick" when you already have it installed, you  
should type "sudo port upgrade ImageMagick" which will cause MacPorts  
to first deactivate the old version before activating the new one. Or  
you can type "sudo port -u upgrade ImageMagick" to do that *and*  
uninstall the old version afterward.