On Thu, Jul 1, 2010 at 2:40 PM, Arttu V. <arttu...@gmail.com> wrote: > On 7/1/10, Grant <emailgr...@gmail.com> wrote: >> Thank you Arttu. Here is the link to the SOAP::WSDL: >> >> http://soap-wsdl.svn.sourceforge.net/viewvc/soap-wsdl/SOAP-WSDL/branches/Typemap.tar.gz?view=tar&pathrev=846 >> >> from the README: >> >> http://code.google.com/p/google-api-adwords-perl/source/browse/trunk/README > > Ok, I see they're shipping the same version which is available from > CPAN as the dev version (2.00.99_3). But the patch is still not made > for its code ... maybe it is for _2 or _1? > > The patch keeps failing out of the box: > > cpan -i Text::Patch > tar xvzf Typemap.tar.gz > tar xvzf awapi_perl_lib_1.3.2.tar.gz > ~/tempski $ awapi_perl_lib_1.3.2/bin/soap_wsdl_patches.pl Typemap > Trying to patch > Typemap/lib/SOAP/WSDL/Generator/Template/XSD/Interface/POD/Operation.tt... > patch successful. > Trying to patch > Typemap/lib/SOAP/WSDL/Generator/Template/XSD/Server.tt... patch > successful. > Trying to patch > Typemap/lib/SOAP/WSDL/Generator/Template/Plugin/XSD.pm... patch > successful. > Trying to patch > Typemap/lib/SOAP/WSDL/XSD/Typelib/Builtin/anyType.pm... patch > successful. > Trying to patch > Typemap/lib/SOAP/WSDL/XSD/Typelib/ComplexType.pm...Hunk #2 failed at > line 425. > ~/tempski $ > > Anyway, only three files' small chunks fail from the patch, and > they're short and mostly just semantically adding some formerly > non-existent subroutines and changing the return values of others. > > I think with some manual labour we could turn that patch into a fixed > regular patch, which we could then apply in an ebuild for SOAP::WSDL > via a USE flag. For example, something along these lines for > dev-perl/SOAP-WSDL-2.00.99.3.ebuild (licenses etc might be wrong): > > # Copyright 1999-2010 Gentoo Foundation > # Distributed under the terms of the GNU General Public License v2 > # $Header: $ > > EAPI=2 > > MODULE_AUTHOR=MKUTTER > MY_P="${P:0:17}_3" > inherit eutils perl-module > > DESCRIPTION="SOAP::WSDL module" > > LICENSE="Artistic" > SLOT="0" > KEYWORDS="amd64 x86" > IUSE="adwords" > > src_prepare() { > perl-module_src_prepare > use adwords && epatch "${FILESDIR}/${PV}-adwords.patch" > } > > > This SOAP-WSDL package could then in turn be made a dependency for > your real google-adwords package (dev-perl/Google-Adwords?): > > RDEPENDS="dev-perl/SOAP-WSDL[adwords]" > > Am I making any sense? > > Theoretically (if you insist), you could still use the perl's > Text::Patch route as well, but (if I'm not entirely wrong, see the > excerpted attempted patch run above) the patch would still need to be > touched up to match properly with the _3 dev release code. And it > would add a dependency to Text::Patch, and make an odd call to perl in > the middle of the ebuild. (I assume it must be made explicitly as I > don't know if perl-module.eclass has any automation for this. Probably > not since AFAICT Text::Patch isn't even installed by default). > > HTH > > -- > Arttu V. -- Running Gentoo is like running with scissors > > I was thinking along the same lines, my use was "google" # Copyright 1999-2010 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: $
EAPI="3" inherit perl-module DESCRIPTION="SOAP-WSDL provides a SOAP client with WSDL support." HOMEPAGE="http://soap-wsdl.svn.sourceforge.net"; SRC_URI="http://soap-wsdl.svn.sourceforge.net/viewvc/soap-wsdl/SOAP-WSDL/branches/Typemap.tar.gz -> ${P}.tar.gz" LICENSE="Apache-2.0" SLOT="0" KEYWORDS="~amd64 ~x86" IUSE="google" DEPEND="${RDEPEND} virtual/perl-Module-Build" RDEPEND="dev-perl/SOAP-Lite dev-perl/Class-Std-Fast" src_prepare() { if use google ; then epatch "${FILESDIR}/${PN}.patch" | die "google patch failed" fi } -- David Abbott (dabbott)
