public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: "Tomáš Chvátal" <scarabeus@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, fonts@gentoo.org
Subject: [gentoo-dev] Re: [RFC] Font eclass EAPI update and design
Date: Mon, 01 Feb 2010 16:14:41 +0300	[thread overview]
Message-ID: <1265030081.10636.23.camel@tablet> (raw)
In-Reply-To: <4B66AE86.9090006@gentoo.org>

В Пнд, 01/02/2010 в 11:35 +0100, Tomáš Chvátal пишет:
> As I was reworking the x-modular-r2 eclass I found out that most of the
> slowdowns for fonts were produced in fonts eclass.

Exactly what slowdowns are you talking about? I've reviewed all changes
and I don't see any noticeable performance improvements anywhere. Or
what do you mean?

> I would like to ask you to review the changes and spot anything that
> might slipped my sight.

1.
-FONT_SUFFIX=${FONT_SUFFIX:-}
+: ${FONT_SUFFIX:=}

What are the benefits of this change? Personally I prefer first syntax
more since it's more evident and does not need to run empty command :

2.
if has X ${IUSE//+} && use X ; then

I'm not sure. With this change should we update all packages depending
on font.eclass to have X in IUSE?

3.
If you dropped

if has_version '>=media-libs/fontconfig-2.4'; then

then >=media-libs/fontconfig-2.4 should be in DEPEND.

4.
+       [[ -n ${DOCS} ]] && { dodoc ${DOCS} || die "docs installation
failed" ; }

This should be non fatal, until somebody installs all packages that
inherit font.eclass and assures us that nothing broke with this change.

-- 
Peter.
h




  reply	other threads:[~2010-02-01 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 10:35 [gentoo-dev] [RFC] Font eclass EAPI update and design Tomáš Chvátal
2010-02-01 13:14 ` Peter Volkov [this message]
2010-02-01 13:29   ` [gentoo-dev] " Tomáš Chvátal
2010-02-01 18:53     ` Peter Volkov
2010-02-01 22:26     ` Ryan Hill
2010-02-02 10:18 ` Torsten Veller
2010-02-02 10:30   ` Tomáš Chvátal
2010-02-02 10:50   ` Fabian Groffen

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=1265030081.10636.23.camel@tablet \
    --to=pva@gentoo.org \
    --cc=fonts@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=scarabeus@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