From: "Diego Petteno (flameeyes)" <flameeyes@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-shells/zsh: ChangeLog zsh-4.3.10.ebuild
Date: Tue, 29 Sep 2009 11:05:05 +0000 [thread overview]
Message-ID: <E1MsaW1-0003Mf-4G@stork.gentoo.org> (raw)
flameeyes 09/09/29 11:05:05
Modified: ChangeLog zsh-4.3.10.ebuild
Log:
Allow using heirloom-doctools instead of groff.
(Portage version: 2.2_rc42/cvs/Linux x86_64)
Revision Changes Path
1.146 app-shells/zsh/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/zsh/ChangeLog?rev=1.146&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/zsh/ChangeLog?rev=1.146&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/zsh/ChangeLog?r1=1.145&r2=1.146
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-shells/zsh/ChangeLog,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -r1.145 -r1.146
--- ChangeLog 3 Jun 2009 06:28:42 -0000 1.145
+++ ChangeLog 29 Sep 2009 11:05:04 -0000 1.146
@@ -1,6 +1,9 @@
# ChangeLog for app-shells/zsh
# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/app-shells/zsh/ChangeLog,v 1.145 2009/06/03 06:28:42 tove Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-shells/zsh/ChangeLog,v 1.146 2009/09/29 11:05:04 flameeyes Exp $
+
+ 29 Sep 2009; Diego E. Pettenò <flameeyes@gentoo.org> zsh-4.3.10.ebuild:
+ Allow using heirloom-doctools instead of groff.
*zsh-4.3.10 (03 Jun 2009)
1.2 app-shells/zsh/zsh-4.3.10.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/zsh/zsh-4.3.10.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/zsh/zsh-4.3.10.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-shells/zsh/zsh-4.3.10.ebuild?r1=1.1&r2=1.2
Index: zsh-4.3.10.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-shells/zsh/zsh-4.3.10.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- zsh-4.3.10.ebuild 3 Jun 2009 06:28:42 -0000 1.1
+++ zsh-4.3.10.ebuild 29 Sep 2009 11:05:04 -0000 1.2
@@ -1,6 +1,6 @@
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/app-shells/zsh/zsh-4.3.10.ebuild,v 1.1 2009/06/03 06:28:42 tove Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-shells/zsh/zsh-4.3.10.ebuild,v 1.2 2009/09/29 11:05:04 flameeyes Exp $
# doc package for -dev version exists?
doc_available=true
@@ -44,7 +44,7 @@
caps? ( sys-libs/libcap )
pcre? ( >=dev-libs/libpcre-3.9 )
gdbm? ( sys-libs/gdbm )"
-DEPEND="sys-apps/groff
+DEPEND="|| ( sys-apps/groff app-doc/heirloom-doctools )
${RDEPEND}"
src_unpack() {
next reply other threads:[~2009-09-29 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 11:05 Diego Petteno (flameeyes) [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 1:44 [gentoo-commits] gentoo-x86 commit in app-shells/zsh: ChangeLog zsh-4.3.10.ebuild Thomas Alan Gall (tgall)
2009-06-03 6:28 Torsten Veller (tove)
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=E1MsaW1-0003Mf-4G@stork.gentoo.org \
--to=flameeyes@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