| 1 |
On 7/1/10, Grant <emailgrant@×××××.com> wrote: |
| 2 |
> Thank you Arttu. Here is the link to the SOAP::WSDL: |
| 3 |
> |
| 4 |
> http://soap-wsdl.svn.sourceforge.net/viewvc/soap-wsdl/SOAP-WSDL/branches/Typemap.tar.gz?view=tar&pathrev=846 |
| 5 |
> |
| 6 |
> from the README: |
| 7 |
> |
| 8 |
> http://code.google.com/p/google-api-adwords-perl/source/browse/trunk/README |
| 9 |
|
| 10 |
Ok, I see they're shipping the same version which is available from |
| 11 |
CPAN as the dev version (2.00.99_3). But the patch is still not made |
| 12 |
for its code ... maybe it is for _2 or _1? |
| 13 |
|
| 14 |
The patch keeps failing out of the box: |
| 15 |
|
| 16 |
cpan -i Text::Patch |
| 17 |
tar xvzf Typemap.tar.gz |
| 18 |
tar xvzf awapi_perl_lib_1.3.2.tar.gz |
| 19 |
~/tempski $ awapi_perl_lib_1.3.2/bin/soap_wsdl_patches.pl Typemap |
| 20 |
Trying to patch |
| 21 |
Typemap/lib/SOAP/WSDL/Generator/Template/XSD/Interface/POD/Operation.tt... |
| 22 |
patch successful. |
| 23 |
Trying to patch |
| 24 |
Typemap/lib/SOAP/WSDL/Generator/Template/XSD/Server.tt... patch |
| 25 |
successful. |
| 26 |
Trying to patch |
| 27 |
Typemap/lib/SOAP/WSDL/Generator/Template/Plugin/XSD.pm... patch |
| 28 |
successful. |
| 29 |
Trying to patch |
| 30 |
Typemap/lib/SOAP/WSDL/XSD/Typelib/Builtin/anyType.pm... patch |
| 31 |
successful. |
| 32 |
Trying to patch |
| 33 |
Typemap/lib/SOAP/WSDL/XSD/Typelib/ComplexType.pm...Hunk #2 failed at |
| 34 |
line 425. |
| 35 |
~/tempski $ |
| 36 |
|
| 37 |
Anyway, only three files' small chunks fail from the patch, and |
| 38 |
they're short and mostly just semantically adding some formerly |
| 39 |
non-existent subroutines and changing the return values of others. |
| 40 |
|
| 41 |
I think with some manual labour we could turn that patch into a fixed |
| 42 |
regular patch, which we could then apply in an ebuild for SOAP::WSDL |
| 43 |
via a USE flag. For example, something along these lines for |
| 44 |
dev-perl/SOAP-WSDL-2.00.99.3.ebuild (licenses etc might be wrong): |
| 45 |
|
| 46 |
# Copyright 1999-2010 Gentoo Foundation |
| 47 |
# Distributed under the terms of the GNU General Public License v2 |
| 48 |
# $Header: $ |
| 49 |
|
| 50 |
EAPI=2 |
| 51 |
|
| 52 |
MODULE_AUTHOR=MKUTTER |
| 53 |
MY_P="${P:0:17}_3" |
| 54 |
inherit eutils perl-module |
| 55 |
|
| 56 |
DESCRIPTION="SOAP::WSDL module" |
| 57 |
|
| 58 |
LICENSE="Artistic" |
| 59 |
SLOT="0" |
| 60 |
KEYWORDS="amd64 x86" |
| 61 |
IUSE="adwords" |
| 62 |
|
| 63 |
src_prepare() { |
| 64 |
perl-module_src_prepare |
| 65 |
use adwords && epatch "${FILESDIR}/${PV}-adwords.patch" |
| 66 |
} |
| 67 |
|
| 68 |
|
| 69 |
This SOAP-WSDL package could then in turn be made a dependency for |
| 70 |
your real google-adwords package (dev-perl/Google-Adwords?): |
| 71 |
|
| 72 |
RDEPENDS="dev-perl/SOAP-WSDL[adwords]" |
| 73 |
|
| 74 |
Am I making any sense? |
| 75 |
|
| 76 |
Theoretically (if you insist), you could still use the perl's |
| 77 |
Text::Patch route as well, but (if I'm not entirely wrong, see the |
| 78 |
excerpted attempted patch run above) the patch would still need to be |
| 79 |
touched up to match properly with the _3 dev release code. And it |
| 80 |
would add a dependency to Text::Patch, and make an odd call to perl in |
| 81 |
the middle of the ebuild. (I assume it must be made explicitly as I |
| 82 |
don't know if perl-module.eclass has any automation for this. Probably |
| 83 |
not since AFAICT Text::Patch isn't even installed by default). |
| 84 |
|
| 85 |
HTH |
| 86 |
|
| 87 |
-- |
| 88 |
Arttu V. -- Running Gentoo is like running with scissors |
Archives