From: "Ryan Hill (dirtyepic)" <dirtyepic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in eclass: font.eclass
Date: Wed, 19 Sep 2007 02:48:21 +0000 [thread overview]
Message-ID: <E1IXpbx-0008Jz-F9@stork.gentoo.org> (raw)
dirtyepic 07/09/19 02:48:21
Modified: font.eclass
Log:
BSD xargs doesn't do -r.
Revision Changes Path
1.33 eclass/font.eclass
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/font.eclass?rev=1.33&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/font.eclass?rev=1.33&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/font.eclass?r1=1.32&r2=1.33
Index: font.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/font.eclass,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- font.eclass 16 Sep 2007 20:00:56 -0000 1.32
+++ font.eclass 19 Sep 2007 02:48:20 -0000 1.33
@@ -1,6 +1,6 @@
# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/font.eclass,v 1.32 2007/09/16 20:00:56 dirtyepic Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/font.eclass,v 1.33 2007/09/19 02:48:20 dirtyepic Exp $
# Author: foser <foser@gentoo.org>
@@ -110,7 +110,7 @@
font_pkg_postinst() {
# unreadable font files = fontconfig segfaults
find "${ROOT}"usr/share/fonts/ -type f '!' -perm 0644 -print0 \
- | xargs -r -0 chmod -v 0644
+ | xargs -0 chmod -v 0644 2>/dev/null
if has_version '>=media-libs/fontconfig-2.4'; then
if [ ${ROOT} == "/" ]; then
@@ -124,7 +124,7 @@
font_pkg_postrm() {
# unreadable font files = fontconfig segfaults
find "${ROOT}"usr/share/fonts/ -type f '!' -perm 0644 -print0 \
- | xargs -r -0 chmod -v 0644
+ | xargs -0 chmod -v 0644 2>/dev/null
if has_version '>=media-libs/fontconfig-2.4'; then
if [ ${ROOT} == "/" ]; then
--
gentoo-commits@gentoo.org mailing list
next reply other threads:[~2007-09-19 2:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 2:48 Ryan Hill (dirtyepic) [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-30 3:46 [gentoo-commits] gentoo-x86 commit in eclass: font.eclass Ryan Hill (dirtyepic)
2010-07-09 3:44 Ryan Hill (dirtyepic)
2010-05-15 5:25 Ryan Hill (dirtyepic)
2010-04-20 4:06 Ryan Hill (dirtyepic)
2010-02-09 17:15 Tomas Chvatal (scarabeus)
2009-10-11 11:44 Markus Meier (maekke)
2009-09-13 4:47 Ryan Hill (dirtyepic)
2009-09-07 21:07 Ryan Hill (dirtyepic)
2009-02-08 18:22 Peter Volkov (pva)
2009-01-12 22:54 Markus Meier (maekke)
2009-01-06 19:24 Fabian Groffen (grobian)
2009-01-02 9:42 Mike Frysinger (vapier)
2009-01-01 9:36 Peter Volkov (pva)
2008-08-19 10:34 Peter Volkov (pva)
2008-06-21 6:12 Peter Volkov (pva)
2008-05-19 0:42 Ryan Hill (dirtyepic)
2008-01-08 17:57 Peter Volkov (pva)
2008-01-08 17:12 Peter Volkov (pva)
2007-12-10 23:58 Ryan Hill (dirtyepic)
2007-09-16 20:00 Ryan Hill (dirtyepic)
2007-09-16 7:07 Ryan Hill (dirtyepic)
2007-09-16 6:21 Ryan Hill (dirtyepic)
2007-09-16 2:20 Ryan Hill (dirtyepic)
2007-09-16 2:18 Ryan Hill (dirtyepic)
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=E1IXpbx-0008Jz-F9@stork.gentoo.org \
--to=dirtyepic@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