public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alexandre Restovtsev" <tetromino@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gnome:master commit in: gnome-extra/gnome-user-docs/
Date: Thu,  6 Oct 2011 03:34:56 +0000 (UTC)	[thread overview]
Message-ID: <ad583cef7568e45102adfc8699169a937cf216b6.tetromino@gentoo> (raw)

commit:     ad583cef7568e45102adfc8699169a937cf216b6
Author:     Alexandre Rostovtsev <tetromino <AT> gmail <DOT> com>
AuthorDate: Thu Oct  6 03:32:16 2011 +0000
Commit:     Alexandre Restovtsev <tetromino <AT> gmail <DOT> com>
CommitDate: Thu Oct  6 03:32:16 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=commit;h=ad583cef

gnome-extra/gnome-user-docs: add a warning on empty LINGUAS

Warn people to set LINGUAS to the set of languages that they actually
need. Building all translations of gnome-user-docs takes quite a long
time even on a quad-core machine.

---
 .../gnome-user-docs/gnome-user-docs-3.2.0.1.ebuild |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)

diff --git a/gnome-extra/gnome-user-docs/gnome-user-docs-3.2.0.1.ebuild b/gnome-extra/gnome-user-docs/gnome-user-docs-3.2.0.1.ebuild
index 56cd5bb..6f9af76 100644
--- a/gnome-extra/gnome-user-docs/gnome-user-docs-3.2.0.1.ebuild
+++ b/gnome-extra/gnome-user-docs/gnome-user-docs-3.2.0.1.ebuild
@@ -28,3 +28,16 @@ DEPEND=">=app-text/gnome-doc-utils-0.20.5
 RESTRICT="binchecks strip"
 
 DOCS="AUTHORS ChangeLog NEWS README"
+
+pkg_pretend() {
+	if [[ -z ${LINGUAS} ]]; then
+		ewarn "You are building ${PN} with LINGUAS unset, so help files"
+		ewarn "in all languages supported by the package will be built."
+		ewarn
+		ewarn "To decrease build time, it is recommended that you set LINGUAS"
+		ewarn "in /etc/make.conf to the set of language codes that are needed"
+		ewarn "for your system. For example,"
+		ewarn "LINGUAS=\"en es\""
+		ewarn "ensures that only English and Spanish translations are built."
+	fi
+}



             reply	other threads:[~2011-10-06  3:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06  3:34 Alexandre Restovtsev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-07 12:41 [gentoo-commits] proj/gnome:master commit in: gnome-extra/gnome-user-docs/ Mart Raudsepp
2018-06-04 11:51 Sobhan Mohammadpour
2018-01-12 13:37 Dennis Lamm
2016-03-27 21:24 Ole Reifschneider
2015-05-03 18:12 Gilles Dartiguelongue
2014-12-22 23:50 Gilles Dartiguelongue
2014-11-23 22:28 Gilles Dartiguelongue
2014-10-15 22:26 Gilles Dartiguelongue
2014-10-06 23:06 Gilles Dartiguelongue
2014-04-24 22:35 Gilles Dartiguelongue
2014-04-07 22:19 Gilles Dartiguelongue
2013-11-14 23:14 Gilles Dartiguelongue
2013-10-14  7:22 Gilles Dartiguelongue
2012-12-23 23:58 Gilles Dartiguelongue
2012-11-22 22:49 Gilles Dartiguelongue
2011-10-19  8:24 Alexandre Restovtsev
2011-10-16  0:18 Alexandre Restovtsev
2011-10-15 22:35 Alexandre Restovtsev
2011-05-30 18:39 Nirbheek Chauhan
2011-04-29 18:29 Nirbheek Chauhan
2011-04-12 23:50 Nirbheek Chauhan
2011-04-10 18:04 Gilles Dartiguelongue
2011-04-05 21:38 Nirbheek Chauhan
2011-03-23  5:20 Nirbheek Chauhan
2011-03-09 11:34 Nirbheek Chauhan
2011-02-22  0:31 Nirbheek Chauhan

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=ad583cef7568e45102adfc8699169a937cf216b6.tetromino@gentoo \
    --to=tetromino@gmail.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