public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dror Levin (spatz)" <spatz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in eclass: base.eclass
Date: Wed, 20 Jan 2010 12:57:13 +0000	[thread overview]
Message-ID: <E1NXa7V-0002bL-Ar@stork.gentoo.org> (raw)

spatz       10/01/20 12:57:13

  Modified:             base.eclass
  Log:
  Fix critical bug in base.eclass where patching with PATCHES would silently fail if file does not exist

Revision  Changes    Path
1.45                 eclass/base.eclass

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/base.eclass?rev=1.45&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/base.eclass?rev=1.45&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/base.eclass?r1=1.44&r2=1.45

Index: base.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/base.eclass,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- base.eclass	13 Jan 2010 09:51:53 -0000	1.44
+++ base.eclass	20 Jan 2010 12:57:13 -0000	1.45
@@ -1,6 +1,6 @@
 # Copyright 1999-2008 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/base.eclass,v 1.44 2010/01/13 09:51:53 scarabeus Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/base.eclass,v 1.45 2010/01/20 12:57:13 spatz Exp $
 
 # @ECLASS: base.eclass
 # @MAINTAINER:
@@ -74,7 +74,6 @@
 	if [[ "$(declare -p PATCHES 2>/dev/null 2>&1)" == "declare -a"* ]]; then
 		for x in "${PATCHES[@]}"; do
 			debug-print "$FUNCNAME: applying patch from ${x}"
-			[[ -f "${x}" ]] && epatch "${x}"
 			if [[ -d "${x}" ]]; then
 				# Use standardized names and locations with bulk patching
 				# Patch directory is ${WORKDIR}/patch
@@ -88,6 +87,8 @@
 				EPATCH_SOURCE=${x}
 				epatch
 				EPATCH_SOURCE=${oldval}
+			else
+				epatch "${x}"
 			fi
 		done
 	else






             reply	other threads:[~2010-01-20 12:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 12:57 Dror Levin (spatz) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-06 21:33 [gentoo-commits] gentoo-x86 commit in eclass: base.eclass Mike Frysinger (vapier)
2011-12-14 23:38 Mike Frysinger (vapier)
2010-05-27  8:09 Tomas Chvatal (scarabeus)
2010-05-25 21:16 Maciej Mrozowski (reavertm)
2010-05-25 20:37 Maciej Mrozowski (reavertm)
2010-04-12 15:33 Tomas Chvatal (scarabeus)
2010-02-02 10:20 Tomas Chvatal (scarabeus)
2010-01-24 13:43 Tomas Chvatal (scarabeus)
2010-01-22  9:34 Tomas Chvatal (scarabeus)
2010-01-20 19:21 Tomas Chvatal (scarabeus)
2010-01-13  1:58 Patrick Lauer (patrick)
2010-01-11 17:23 Tomas Chvatal (scarabeus)
2010-01-11 16:57 Tomas Chvatal (scarabeus)
2010-01-03 21:07 Michael Sterrett (mr_bones_)
2009-05-17  9:25 Peter Alfredsen (loki_val)
2009-01-18 18:21 Peter Alfredsen (loki_val)
2009-01-17 16:56 Michael Sterrett (mr_bones_)
2008-11-09 15:47 Peter Alfredsen (loki_val)
2008-07-17  9:49 Peter Volkov (pva)
2008-02-16 20:12 Petteri Raty (betelgeuse)
2008-02-12 23:51 Petteri Raty (betelgeuse)
2007-09-12 20:05 Petteri Raty (betelgeuse)

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=E1NXa7V-0002bL-Ar@stork.gentoo.org \
    --to=spatz@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