On Sunday 12 Jul 2015 20:40:35 James wrote: > Hello, > > > So lately I've been using elogv for a convenience way to ensure no > issues with the most recent packages installed or upgraded. It's a neat > little tool. Today I found this: > > dev-lang/php-5.6.10 - 07/10/2015 {in purple} > > snipped::> > > "This package has a configure.in file which has long been deprecated. > Pleas │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." > > OK, so I looked the bug. From what I read : > > If we start now, to rename configure.in to configure.ac before > > eautoreconf we will avoid lots of breakages due to the deprecation of > > .in in automake-1.13. > > Makes sense; but I cannot find the file. I get lots of hits for a > "configure.in" in my code trees, but little on the rest of the system; here > are the few: > > /usr/portage/dev-lang/lua/files/configure.in > /usr/share/cppunit/examples/money/configure.in > (and quit a few on firefox. > > # equery depends =sys-devel/autoconf-2.13 > * These packages depend on sys-devel/autoconf-2.13: > app-admin/tripwire-2.4.2.2-r3 (sys-devel/autoconf) > app-editors/vim-7.4.273 (sys-devel/autoconf) > app-editors/vim-core-7.4.273 (sys-devel/autoconf) > mail-client/thunderbird-31.7.0 (=sys-devel/autoconf-2.1*) > net-libs/libnet-1.1.6 (sys-devel/autoconf) > net-misc/openssh-6.7_p1 (sys-devel/autoconf) > sys-apps/attr-2.4.47-r1 (sys-devel/autoconf) > www-client/firefox-31.7.0 (=sys-devel/autoconf-2.1*) > www-client/seamonkey-2.33.1-r1 (=sys-devel/autoconf-2.1*) > > > Huh? really? I have versions 2.13 and 2.69 of sys-devel/autoconf installed > > > So, I'm kinda head scratching to decide what, if anything to fix? > There much that I did not post, but they are all dead ends like: > > "For more details on how minor version slotting works (PHP_TARGETS) please > read the upgrade guide: http://www.gentoo.org/proj/en/php/php-upgrading.xml > " from the elogview of the latest php install. That link is dead. > > Any suggestions? Is elogv borked in this case? > > /var/tmp/portage/php-5.6.10/work/php-5.1.6/config.log does not even > exist.... > > # eselect php list cli > [1] php5.6 * > > Bottom line is I have not use php directly in some time, so it is quite > easy that I missed some info from the devs on php changes..... I did not > see anything in the news system nor pgo.
Did you start an emerge of php and then looked in your /var/tmp/portage to find it? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.