On Dec 1, 2006, at 12:18 AM, David Reiser wrote:
>
> On Nov 30, 2006, at 7:36 AM, Chris Zubrzycki wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On Nov 29, 2006, at 10:22 PM, David Reiser wrote:
>>
>>> Configure checks for the presence of 2 versions of libsoup, and if
>>> n
On Nov 30, 2006, at 7:36 AM, Chris Zubrzycki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Nov 29, 2006, at 10:22 PM, David Reiser wrote:
>
>> Configure checks for the presence of 2 versions of libsoup, and if
>> neither is present, testgtkhtml.c isn't compiled. Furthermore, w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 29, 2006, at 10:22 PM, David Reiser wrote:
> Configure checks for the presence of 2 versions of libsoup, and if
> neither is present, testgtkhtml.c isn't compiled. Furthermore, when
> it is compiled, it is compiled into the top src directory,
On Nov 29, 2006, at 11:52 AM, Sebastien Maret wrote:
> David Reiser <[EMAIL PROTECTED]> writes:
> [...]
>
>> I've found that if I strip the crypto dependencies from the info file
>> and add BuildConflicts: libsoup-everything-but-shlibs,
>> gtkhtml3.8.15-3.10.2 will build and the resulting library
David Reiser <[EMAIL PROTECTED]> writes:
> gtkhtml3 and 3.8.15 are in crypto because of a builddepends on
> libsoup (and its crypto dependencies). The packaging description
> mentions that the crypto portions are only used for testing during
> compile. Running otool -L on the gtkhtml library
gtkhtml3 and 3.8.15 are in crypto because of a builddepends on
libsoup (and its crypto dependencies). The packaging description
mentions that the crypto portions are only used for testing during
compile. Running otool -L on the gtkhtml library shows no links to
crypto libraries.
Crypto pol
