public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/pkg_pretend/
Date: Thu, 25 Jul 2013 08:28:39 +0000 (UTC)	[thread overview]
Message-ID: <1374738544.c71bffa07227ab76732ec9afff4a926f0c55a64a.jlec@gentoo> (raw)

commit:     c71bffa07227ab76732ec9afff4a926f0c55a64a
Author:     Thomas D <whissi <AT> whissi <DOT> de>
AuthorDate: Thu Jul 25 07:49:04 2013 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Thu Jul 25 07:49:04 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=c71bffa0

pkg_pretend sample used deprecated error message format

Since linux-info.eclass's revision 1.35, which fixed bug #113142, ERROR_* is the preferred format for error message variable names.

---
 ebuild-writing/functions/pkg_pretend/text.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ebuild-writing/functions/pkg_pretend/text.xml b/ebuild-writing/functions/pkg_pretend/text.xml
index 9f051f7..0279145 100644
--- a/ebuild-writing/functions/pkg_pretend/text.xml
+++ b/ebuild-writing/functions/pkg_pretend/text.xml
@@ -53,7 +53,7 @@ pkg_pretend() {
 		if [[ -e "${ROOT}"/usr/src/linux/.config ]] ; then
 			if kernel_is lt 2 6 30 ; then
 				CONFIG_CHECK="FUSE_FS"
-				FUSE_FS_ERROR="this is an unrealistic testcase..."
+				ERROR_FUSE_FS="this is an unrealistic testcase..."
 				check_extra_config
 			fi
 		fi


             reply	other threads:[~2013-07-25  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  8:28 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-30 18:21 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/pkg_pretend/ Markos Chandras
2016-02-23  7:17 Ulrich Müller

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=1374738544.c71bffa07227ab76732ec9afff4a926f0c55a64a.jlec@gentoo \
    --to=jlec@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