# Look for missing pak files.
for lang in ${CHROMIUM_LANGS}; do
if [[ ! -e ${lang}.pak ]]; then
- # https://bugs.gentoo.org/583762
- if [[ ${lang} != sr-ME || ! -e me.pak ]]; then
- eqawarn "L10N warning: no .pak file for ${lang} (${lang}.pak not found)"
- fi
+ eqawarn "L10N warning: no .pak file for ${lang} (${lang}.pak not found)"
fi
done
# Bug 588198
rm -f fake-bidi.pak || die
+ rm -f fake-bidi.pak.info || die
# Look for extra pak files.
# Remove pak files that the user does not want.
continue
fi
- # https://bugs.gentoo.org/583762
- if [[ ${lang} == me ]]; then
- if ! has sr-ME ${CHROMIUM_LANGS}; then
- eqawarn "L10N warning: no sr-ME in LANGS"
- elif ! use l10n_sr-ME; then
- rm "${pak}" || die
- fi
- continue
- fi
-
if ! has ${lang} ${CHROMIUM_LANGS}; then
eqawarn "L10N warning: no ${lang} in LANGS"
continue
fi
+
if ! use l10n_${lang}; then
rm "${pak}" || die
+ rm -f "${pak}.info" || die
fi
done
}
fi
# Prevent user problems like bug #348235.
- eshopts_push -s extglob
- if is-flagq '-g?(gdb)?([1-9])'; then
+ if ( shopt -s extglob; is-flagq '-g?(gdb)?([1-9])' ); then
ewarn
ewarn "You have enabled debug info (i.e. -g or -ggdb in your CFLAGS/CXXFLAGS)."
ewarn "This produces very large build files causes the linker to consume large"
ewarn "Please try removing -g{,gdb} before reporting a bug."
ewarn
fi
- eshopts_pop
# ccache often causes bogus compile failures, especially when the cache gets
# corrupted.