Summary: | sys-apps/portage shouldn't save all repeated messages if they are the same | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Toralf Förster <toralf> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toralf Förster
2015-07-27 11:21:05 UTC
With a more explicit, direct run of ebuild cone-0.90-r1: >>> Preparing source in /var/tmp/portage/mail-client/cone-0.90-r1/work/cone-0.90 ... * Applying cone-0.84.20100819-aspell-automagic.patch ... [ ok ] * Applying cone-0.86-skip-rfc2045-test.patch ... [ ok ] * Applying cone-0.90-gnutls3.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/mail-client/cone-0.90-r1/work/cone-0.90/unicode' ... * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal ... [ ok ] * This package has a configure.in file which has long been deprecated. Please * update it to use configure.ac instead as newer versions of autotools will die * when it finds this file. See https://bugs.gentoo.org/426262 for details. * Running autoconf --force ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign --force-missing ... [ ok ] * Running eautoreconf in '/var/tmp/portage/mail-client/cone-0.90-r1/work/cone-0.90/numlib' ... * Running libtoolize --install --copy --force --automake ... [ ok ] * Running aclocal ... [ ok ] * This package has a configure.in file which has long been deprecated. Please * update it to use configure.ac instead as newer versions of autotools will die * when it finds this file. See https://bugs.gentoo.org/426262 for details. (and continues on) Note, that it is running eautoreconf, libtoolize, and aclocal for every directory, hence the spammed message, one each time it runs and detects the file. Well... I am not sure what could be done in portage side... maybe some kind of code being able to detect the messages are exactly the same and, then, only recording one... ? :/ |