Re: RFS: gsoap (updated package)
Hello,
Stefano Canepa wrote:
> Il giorno lun, 22/02/2010 alle 17.52 +0100, Steffen Moeller ha scritto:
>>> I would be glad if someone uploaded this package for me.
>> the diff.gz has many *.cpp files in, and there are both Makefile.in and
>> Makefile, configure and configure.in. I have not looked at it in more
>> detail, but could there be a way that you reduce the length of the diff.gz
>> to something one can oversee with the eye? The current version has 37522
>> lines, which given all the *.cpp files in are just too tough for a sponsor
>> to check through.
>
> I checked the diff.gz, this is the result of the need to cut out all
> apache_13 module code. I tried to convince upstream author to drop this
> code in next release but I did not succeded. We agree to delete all
> files lintian complains about.
> If you would like to write to upstream author to convice him to delete
> useless code in future release please do and I'll be gratefull to you
> for your favour. Tomorrow I'll ask again Mandriva gsoap maintainer (a
> collegue of mine) to ask for the same thing even if he told me that
> inclusion of old apache code is not a problem in his package.
I cannot tell why some directory you need to remove. I just want an
interpretable diff.gz :) What happens if you take a brand new source
tree and just move the current debian folder over to that one. Will it
produce a working package? If so, then I suggest to go for that approach
and leave old sources in.
>> A file debian/README.source should explain all the differences done to the
>> source tree for its inclusion to Debian. I know, as a past NMUer, that the
>> package already wasn't in the best of all possible shapes when you took it
>> up. If you could give it some more love to make the diff.gz nice to read,
>> then this would be real helpful.
>
> I'm going to write more details in my README.source. It took me a long
> time to read the diff, you're right it's quite impossible to read.
Colleagues of mine use gsoap as a dynamic library. Are you also
providing dynamic libraries? Well, I'll see :)
Steffen
Reply to: