[120217] trunk/dports/graphics/tiff/Portfile

Ryan Schmidt ryandesign at macports.org
Mon May 19 16:10:34 PDT 2014


On May 19, 2014, at 18:05, MK-MacPorts at techno.ms wrote:

> Hi Ryan,
> 
> On 20 May 2014, at 01:01 , Ryan Schmidt <ryandesign at macports.org> wrote:
>> Yeah, it's good if commit messages can explain why a change is being made.
> Yes, I know. Was a little to fast there, i admit.
> 
>> Just saying that you're revbumping a port isn't informative; I'd like to be able to see e.g. which library had been updated thus requiring a rebuild.
> That’s why I sent the additional post just a moment ago.
> 
>> We do currently have the problem that tiff links with XQuartz if present. I verified that's even the case for the Mavericks package we're distributing.
> That’s what I am running here.
> 
>> So if you used to have XQuartz, then uninstalled it, or if you don't have XQuartz installed but got our tiff package from the buildbot which does, that could account for the problem.
> Yep, the latter is the case.
> 
>> I've been trying to solve this problem, but tiff's build system is horrible and is not making it easy for me. Here's the ticket under which I'm working on this:
>> https://trac.macports.org/ticket/43642
> I CC’ed myself to it.
> 
> Sorry revbumping for nothing.

It's ok, at least we confirmed that the problem you were seeing is the one I'm already working on, and not something new.

I undid the revbump, to save users from needlessly reinstalling the port if they haven't already.



More information about the macports-dev mailing list