From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-pms] [PATCH] pkg-mgr-commands: Replace MAKEOPTS conf var with explicit description
Date: Sat, 14 May 2016 00:00:02 +0200 [thread overview]
Message-ID: <1463176802-19338-1-git-send-email-mgorny@gentoo.org> (raw)
Replace the mentioning of MAKEOPTS configuration variable with generic
description of 'make options'. This is in line with other parts of the
specification where we avoid referencing package manager configuration
explicitly. Furthermore, MAKEOPTS was only mentioned this one time with
no explanatory description and no guarantee of being exported to the
ebuild environment, so it is better to avoid making developers think it
is reliable.
---
pkg-mgr-commands.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
index 78b5a3b..263c97c 100644
--- a/pkg-mgr-commands.tex
+++ b/pkg-mgr-commands.tex
@@ -304,7 +304,7 @@ current phase function has returned.
\item[emake] Calls the \t{\$MAKE} program, or GNU make if the \t{MAKE} variable is unset.
Any arguments given are passed directly to the make command, as are the user's chosen
- \t{MAKEOPTS}\@. Arguments given to \t{emake} override user configuration. See also
+ make options. Arguments given to \t{emake} override user configuration. See also
section~\ref{sec:guaranteed-system-commands}. \t{emake} must be an external program and cannot
be a function or alias---it must be callable from e.\,g.\ \t{xargs}. Failure behaviour is EAPI
dependent as per section~\ref{sec:failure-behaviour}.
--
2.8.2
next reply other threads:[~2016-05-13 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 22:00 Michał Górny [this message]
2016-05-13 22:33 ` [gentoo-pms] [PATCH] pkg-mgr-commands: Replace MAKEOPTS conf var with explicit description Ulrich Mueller
2016-05-14 5:08 ` Michał Górny
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=1463176802-19338-1-git-send-email-mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-pms@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