Updated ktoblzcheck && gnucash
Bryan Blackburn
0x62_0x6c_0x62 at pobox.com
Thu Nov 30 23:00:30 PST 2006
On Nov 30, 2006, at 10:53 PM, Ryan Schmidt wrote:
> On Nov 30, 2006, at 09:31, Anthony Agelastos wrote:
>
>> I have noticed that ktoblzcheck and gnucash were updated today and
>> issued a `port upgrade installed`. This is what I see.
>>
...
>> Error: No port libtiff found.
>> ---> Fetching gnucash
>> ---> Verifying checksum(s) for gnucash
>> ---> Extracting gnucash
>> ---> Configuring gnucash
>> ---> Building gnucash with target all
>>
>> I have the 'tiff' port installed (and did a search and did not
>> find a libtiff as a MacPort), so I want to make sure that the
>> error is not problematic. Does anyone have any comments regarding
>> this? Two independent Intel Macs that I am privy to display this
>> same error message. Thank you for your assistance with this.
>
> Let's see...
>
> I grepped all Portfiles for the string "libtiff" [1] and the only
> one that doesn't try to include libtiff by saying "lib:libtiff" [2]
> is gnome/yelp, which says "port:libtiff". This of course doesn't
> work because as you saw there is no port called "libtiff"; the port
> is called "tiff". This change was made in revision 19754 on
> 2006-09-27.
>
Note, for dependencies you don't need to do quite this much work, as
that information is in the PortIndex file:
$ grep "port:libtiff" /path/to/PortIndex
should do for this issue, as well as looking for
"lib:libtiff:libtiff" in case that pattern was used instead.
Bryan
> Looks like gnucash requires gnucash-docs, and gnucash-docs requires
> yelp.
>
> I can't see how this could ever work, so I changed "port:libtiff"
> to "port:tiff" in revision 20823. I'm not sure how long it takes to
> be available to you, but try a port sync in a couple hours and see
> if you can now build yelp, and thus gnucash.
>
>
> [1] find . -name Portfile -print0 | xargs -0 grep libtiff | grep -v
> 'lib:libtiff' | grep -v .svn
>
> [2] There are also several that include libtiff by referencing
> "port:tiff" which is fine too.
>
>
More information about the macports-users
mailing list