Is the right way to do this... [[ ${CHOST} == *-mint* ]]; then elibtoolize or is it good enought to just generalize to everybody ?
elibtoolize is light enough to just run it unconditionally without any problems
... %% ebuild mpfr-2.4.2_p3.ebuild digest unpack Appending /home/jolexa/portage/global/prefix-trunk to PORTDIR_OVERLAY... >>> Creating Manifest for /home/jolexa/portage/global/prefix-trunk/dev-libs/mpfr * mpfr-2.4.2.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking mpfr-2.4.2.tar.bz2 ;-) ... [ ok ] * CPV: dev-libs/mpfr-2.4.2_p3 * REPO: gentoo_prefix * USE: amd64 elibc_glibc kernel_linux prefix userland_GNU >>> Unpacking source... >>> Unpacking mpfr-2.4.2.tar.bz2 to /public/tmp/linux-64/portage/dev-libs/mpfr-2.4.2_p3/work * Applying patch01 ... [ ok ] * Applying patch02 ... [ ok ] * Applying patch03 ... [ ok ] * Running elibtoolize in: mpfr-2.4.2 * Portage patch failed to apply (ltmain.sh version 2.2.6 Debian-2.2.6a-4)! * Please bug azarah or vapier to add proper patch. * ERROR: dev-libs/mpfr-2.4.2_p3 failed: * Portage patch failed to apply! * * Call stack: * ebuild.sh, line 54: Called call-ebuildshell 'src_unpack' * environment, line 401: Called src_unpack * environment, line 2827: Called elibtoolize * environment, line 1093: Called die * The specific snippet of code: * die "Portage patch failed to apply!"; * * If you need support, post the output of 'emerge --info =dev-libs/mpfr-2.4.2_p3', * the complete build log and the output of 'emerge -pqv =dev-libs/mpfr-2.4.2_p3'. * The complete build log is located at '/public/tmp/linux-64/portage/dev-libs/mpfr-2.4.2_p3/temp/build.log'. * The ebuild environment file is located at '/public/tmp/linux-64/portage/dev-libs/mpfr-2.4.2_p3/temp/environment'. * S: '/public/tmp/linux-64/portage/dev-libs/mpfr-2.4.2_p3/work/mpfr-2.4.2'
I don't see why elibtoolize isn't run for most packages anyway, but from what darkside posted it seems as though there's a bug that vapier needs to fix, as I'd agree that it should just work everywhere.
I'm not sure if we should update the patches to work with debian patched ltmain.sh. vapier?
vapier ?
cant say i relish the idea. is the problem just because of the version tag, or because the patch doesnt actually apply ? if it's the former, we can just chomp the version down to the first spcae-delimited item.
It appears the patch failing was a glitch, as it is not reproducable any more. Makes this bug trivial again. Sorry for the bother.
