From owner-freebsd-ports@FreeBSD.ORG Mon Jul 16 08:04:07 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id C60BD106566B for ; Mon, 16 Jul 2012 08:04:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 2A19914E9B9; Mon, 16 Jul 2012 08:04:07 +0000 (UTC) Message-ID: <5003CAF6.5040907@FreeBSD.org> Date: Mon, 16 Jul 2012 01:04:06 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Ruslan Mahmatkhanov References: <4FC1F4EF.90504@dougbarton.us> <5000838D.2090108@yandex.ru> <5002426F.60502@dougbarton.us> <5003BE1D.3020802@yandex.ru> In-Reply-To: <5003BE1D.3020802@yandex.ru> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: churanov.port.maintainer@gmail.com, Doug Barton , FreeBSD ports list Subject: Re: Problems with new boost X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 08:04:07 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/16/2012 00:09, Ruslan Mahmatkhanov wrote: > It's Mario Lobo (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-----