Problems with new boost

[Doug Barton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/16/2012 00:09, Ruslan Mahmatkhanov wrote:
> It's Mario Lobo <lobo at bsd.com.br> (submitter of ports/169755), not me to
> thank :). I didn't reported upstream. And looking at the fix - as far I
> understand it actually just updating our local FreeBSD-specific changes
> according to upstream changes. So I think that all our local patches (16
> items) should be sent upstream for review/inclusion, because we can come
> up to another weird behaviour with future boost updates. But
> unfortunately I'm not the proper person to do that (I'm not sure what
> this patches do and can't substantiate their necessity to upstream).

I can't think of anyone better to do this than you. :)  The info you
need should be in the logs. If you wrap the changes in #ifdef freebsd
and submit them upstream most projects are receptive (in my experience).

Doug

- -- 

    Change is hard.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBCAAGBQJQA8r2AAoJEFzGhvEaGryE7C4IAJnJq/C4rty9RxiyKX6QhPNt
wyQGZHdtmSMBkxzLV9sBTex/st6ZBsFI+bDLk6n3oLl/35Xn7YIWp9En6PUVhK/J
K5es/QiL83iszCTAu+OTrUm2r1yVt0Te74g5RaiwrLZoKpaYVlzbbEGbGF7wAPf+
Fi+SI2grvOtVbNSiJyHuJ6igG3vQvwcfe1Qaa9EUMFtPDMfkQlktV7GEeuoTiIKx
As0LnQ6iPySZtYNRER2LeZJMBBpBF0ESLwZYENXJNDKznOcD8YdZnqZypLw4Z0Ae
D0cy/QrkYceb89MhszHmZRNEY59Et33F2pInX0gQUt8KOZJUZb2feprFi4AN0nk=
=pKLN
-----END PGP SIGNATURE-----