* Tomáš Chvátal scarab...@gentoo.org:
# @FUNCTION: font_pkg_setup
# @DESCRIPTION:
# The font pkg_setup function.
# Collision portection and Prefix compat for eapi 3.
font_pkg_setup() {
# make sure we get no collisions
# setup is not the nicest place, but preinst doesn't cut it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 2.2.2010 11:18, Torsten Veller napsal(a):
* Tomáš Chvátal scarab...@gentoo.org:
# @FUNCTION: font_pkg_setup
# @DESCRIPTION:
# The font pkg_setup function.
# Collision portection and Prefix compat for eapi 3.
font_pkg_setup() {
# make
On 02-02-2010 11:18:32 +0100, Torsten Veller wrote:
# Prefix compat
case ${EAPI:-0} in
0|1|2)
if ! use prefix; then
EPREFIX=
ED=${D}
EROOT=${ROOT}
В Пнд, 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dne 1.2.2010 14:14, Peter Volkov napsal(a):
В Пнд, 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
В Пнд, 01/02/2010 в 14:29 +0100, Tomáš Chvátal пишет:
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?
Nak this specialy allows that you dont have to keep X in iuse.
But it does not matter
On Mon, 01 Feb 2010 14:29:19 +0100
Tomáš Chvátal scarab...@gentoo.org wrote:
Dne 1.2.2010 14:14, Peter Volkov napsal(a):
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
