I just tagged a new version that should be smarter about how it fails when 
ImageMagick isn't installed. Pkg.update() will get it for you.

--Tim

On Sunday, March 16, 2014 09:08:45 PM Nathaniel Virgo wrote:
> On 16 March 2014 20:07, Tim Holy <[email protected]> wrote:
> 
> Hi Nathaniel,
> 
> > On Saturday, March 15, 2014 11:42:42 PM Nathaniel Virgo wrote:
> > > Although the Homebrew issue is apparently fixed, I still get the
> > > following error.
> > 
> > I just don't know enough about Homebrew to be able to advise you here.
> 
> No problem! As a newcomer, it wasn't obvious to me whether the error was
> coming from Homebrew rather than anything else.
> 
> Run those diagnostic commands _after_ you get this error---the whole point
> 
> > is
> > to see the variable settings that contributed to this problem.
> 
> I see. Sorry, I assumed I wouldn't be able to run the other commands if the
> first failed. Here is the output:
> 
> julia> Images.LibMagick.have_imagemagick
> false
> 
> julia> Images.LibMagick.libwand
> ""
> 
> I have to say that your experience here makes me think Images needs to be
> 
> > split into several parts, so that binary dependencies do not get in the
> > way of
> > people who just want to use it for its algorithms. Sadly, I'm just not
> > sure
> > I'll have time to get to that in the next week or two.
> 
> That sounds like it would make sense once you have the time. (I'm not in a
> hurry personally.)
> 
> Nathaniel

Reply via email to