On 12/15/14 18:13, Kenneth Westerback wrote: > On 15 December 2014 at 13:02, ni...@openbsd.org <ni...@openbsd.org> wrote: >> On 12/14/14 19:07, Kenneth Westerback wrote: >>> On 14 December 2014 at 13:50, Nigel Taylor >>> <njtay...@asterisk.demon.co.uk> wrote: >>>> Time to remove GNOME I from ports, it's old and ancient, and not >>>> maintained anymore. >>>> >>>> libghttp was the forerunner to libsoup and part of GNOME I, used to >>>> speed up p5-libwww, provided by including www/p5-HTTP-GHTTP, a wrapper >>>> around www/libghttp. This is the only remaining port using this GNOME I >>>> library. The dependency has lingered on but not used. >>>> >>>> Once p5-libwww has been updated, the www/p5-HTTP-GHTTP port can be >>>> removed and then followed by www/libghttp. >>>> >>>> I been using p5-libwww without libghttp/p5-HTTP-GHTTP for sometime on >>>> amd64. >>>> >>>> Only asking for Ok / Comments on www/p5-libwww >>>> >>> >>> Without commenting on technical desirability, although your >>> justification seems plausible to me, I can say I would *love* to see >>> this because p5-HTTP-GHTTP has been crapping out of my dpb builds for >>> some weeks now for reasons I haven't figured out, beyond knowing it >>> was related to libghttp. :-) >>> >>> .... Ken >>> >> Looking back at dpb logs p5-HTTP-GHTTP / libghttp built first time, 3 >> time in a row, and can't recall ever having failed, doesn't mean I don't >> believe your having problems. I have seen the same in my dpb builds with >> other ports far too often, where you can't explain why they failed other >> than using dpb. >> >> Removing p5-HTTP-GHTTP is likely to just shift the problem elsewhere. >> > > I wouldn't be surprised. No idea what it is about my environment that > causes the problem, so it could easily migrate. I've even tried not > using tmpfs for /tmp without any change. > > "checking for main() in -lghttp... libghttp not found" > > is what happens. Even though I can *SEE* libghttp is in place. Perhaps > it's caught up in caching for somehow. I guess I could dial my > bufcachepercent down from 90. And when I kick it into retrying by > 'make clean' in /usr/ports/www/p5-HTTP-GHTTP and removing all the > "*GHTTP*" logs, it eventually works even though the libghttp is > untouched by anything in the meantime. > > Even if p5-HTTP-GHTTP is the *only* port I try to build with dpb it > fails. Sigh. I'd be happy to move on to another problem child, just > for variety. :-). > > .... Ken > >
committed changes. So these two ports no longer required.
