public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Markos Chandras (hwoarang)" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-libs/boost: boost-1.48.0-r1.ebuild ChangeLog
Date: Sat,  4 Feb 2012 19:31:46 +0000 (UTC)	[thread overview]
Message-ID: <20120204193146.D3D8E2004C@flycatcher.gentoo.org> (raw)

hwoarang    12/02/04 19:31:46

  Modified:             boost-1.48.0-r1.ebuild ChangeLog
  Log:
  Backport fix for BOOST_FOREACH from upstream.
  
  (Portage version: 2.2.0_alpha84/cvs/Linux x86_64)

Revision  Changes    Path
1.2                  dev-libs/boost/boost-1.48.0-r1.ebuild

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/boost-1.48.0-r1.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/boost-1.48.0-r1.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/boost-1.48.0-r1.ebuild?r1=1.1&r2=1.2

Index: boost-1.48.0-r1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/boost/boost-1.48.0-r1.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- boost-1.48.0-r1.ebuild	23 Jan 2012 22:23:22 -0000	1.1
+++ boost-1.48.0-r1.ebuild	4 Feb 2012 19:31:46 -0000	1.2
@@ -118,6 +118,7 @@
 }
 
 src_prepare() {
+	epatch "${FILESDIR}/${P}-BOOST_FOREACH.patch"
 	epatch "${FILESDIR}/${P}-mpi_python3.patch"
 	epatch "${FILESDIR}/${P}-respect_python-buildid.patch"
 	epatch "${FILESDIR}/${P}-support_dots_in_python-buildid.patch"



1.236                dev-libs/boost/ChangeLog

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/ChangeLog?rev=1.236&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/ChangeLog?rev=1.236&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/boost/ChangeLog?r1=1.235&r2=1.236

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-libs/boost/ChangeLog,v
retrieving revision 1.235
retrieving revision 1.236
diff -u -r1.235 -r1.236
--- ChangeLog	23 Jan 2012 22:23:22 -0000	1.235
+++ ChangeLog	4 Feb 2012 19:31:46 -0000	1.236
@@ -1,6 +1,10 @@
 # ChangeLog for dev-libs/boost
 # Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-libs/boost/ChangeLog,v 1.235 2012/01/23 22:23:22 hwoarang Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-libs/boost/ChangeLog,v 1.236 2012/02/04 19:31:46 hwoarang Exp $
+
+  04 Feb 2012; Markos Chandras <hwoarang@gentoo.org>
+  +files/boost-1.48.0-BOOST_FOREACH.patch, boost-1.48.0-r1.ebuild:
+  Backport fix for BOOST_FOREACH from upstream.
 
 *boost-1.48.0-r1 (23 Jan 2012)
 






             reply	other threads:[~2012-02-04 19:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 19:31 Markos Chandras (hwoarang) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-14 19:57 [gentoo-commits] gentoo-x86 commit in dev-libs/boost: boost-1.48.0-r1.ebuild ChangeLog Markos Chandras (hwoarang)
2012-04-02  0:53 Mike Gilbert (floppym)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120204193146.D3D8E2004C@flycatcher.gentoo.org \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox