public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Julian Ospald" <julian.ospald@googlemail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/
Date: Fri, 23 Nov 2012 18:02:50 +0000 (UTC)	[thread overview]
Message-ID: <1353693757.b373edb4fbb2f619b0f153985a9e1b5d8c8f3220.hasufell@gentoo> (raw)

commit:     b373edb4fbb2f619b0f153985a9e1b5d8c8f3220
Author:     hasufell <julian.ospald <AT> googlemail <DOT> com>
AuthorDate: Fri Nov 23 18:02:37 2012 +0000
Commit:     Julian Ospald <julian.ospald <AT> googlemail <DOT> com>
CommitDate: Fri Nov 23 18:02:37 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=b373edb4

clarify verbose-build log part of common mistakes

people should not randomly report bugs if the affected package
uses a build system controllable by portage or an eclass
wrt bug #444354

---
 ebuild-writing/common-mistakes/text.xml |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
index 5443a98..fbe9a0a 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -86,8 +86,10 @@ or use EAPI 5 where that argument is passed automatically. 'emake V=1' should al
 For custom Makefiles you often have to write a patch. Try to get upstream to include an
 option like 'V=1' to enable full verbosity.
 </p>
-<note> If you notice non-verbose build log in any package open a bug and make it block the
-tracker bug #429308</note>
+<note>In case you encounter an affected package which uses a build system not
+controllable by portage or eclasses you should file a bug (preferably with a patch)
+and make it block the tracker bug #429308. Solutions above ebuild level are
+preferred.</note>
 </body>
 </subsection>
 


             reply	other threads:[~2012-11-23 18:03 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 18:02 Julian Ospald [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-24 14:15 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/ Ulrich Müller
2022-01-22 23:43 Sam James
2021-12-22 15:38 Ulrich Müller
2021-09-17  9:09 Ulrich Müller
2021-08-14 10:00 Ulrich Müller
2021-08-01  2:43 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-08-01  2:38 Sam James
2021-03-30 18:20 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-21  6:06 Ulrich Müller
2021-02-06 10:35 Ulrich Müller
2017-01-25  5:31 Göktürk Yüksek
2017-01-25  5:31 Göktürk Yüksek
2017-01-21 19:21 Göktürk Yüksek
2016-10-28 17:13 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2014-10-18 17:36 Markos Chandras
2014-05-13 19:32 Ulrich Müller
2013-09-28 12:19 Markos Chandras
2012-12-30 14:21 Julian Ospald
2012-12-04 19:26 Julian Ospald
2012-11-17 19:00 Markos Chandras
2012-11-11 19:33 Markos Chandras
2012-11-07 13:27 Michael Palimaka
2012-11-07 13:25 Michael Palimaka
2012-08-08 19:20 Markos Chandras
2011-03-09 16:42 Jeremy Olexa

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=1353693757.b373edb4fbb2f619b0f153985a9e1b5d8c8f3220.hasufell@gentoo \
    --to=julian.ospald@googlemail.com \
    --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