Adam D. Barratt wrote:
> Hi,

Hi

> 1) Is it worth discussing, or at least mentioning, this on -devel? I'm
> more than happy with "no" as an answer ;-)

It's not necessary IMHO.

> 2) Do we want to provide a fallback to the current parsing code in the
> event that the user doesn't have libsoap-lite-perl installed? My
> personal preference would be not to, if only because doing so leaves us
> still having to maintain the HTML scraping.

Also not necessary IMHO.

> Anyway, on to the individual scripts:
> 
> tagpending
> ----------
> 
> Rewrite in perl. Mostly done, and not as mad as it sounds. :-)
> 
> tagpending already contains four perl invocations (two bts select calls
> and one each to dpkg-parsechangelog and URI::Escape; the latter
> shouldn't be necessary after moving to SOAP). Personally, I'd also be
> more comfortable implementing #439688 (including changelog entries as
> comments in the generated e-mail) in perl than in shell.

I'm indifferent about it being shell or perl, though am happy I can
worry about a bug less as you seem to want to fix it if it's perl :-)

> debchange
> ---------
> 
> Mostly implemented (as you may have spotted from my accidental check-in
> of the partially finished change; oops). Waiting for source package
> names to be available via SOAP (see #465332).

Ok, what's the progress on that bug?

> bts
> ---
> 
> The perennial trigger for discussions about replacing HTML scraping with
> SOAP. Sadly the fact that bts (rather usefully :) supports offline
> working and local caches of bug content means we're largely stuck with
> parsing the generated HTML. 

Wouldn't it be better to have a cache of the SOAP answers in that case?

> wnpp-alert
> ----------
> 
> Parses http://www.debian.org/devel/wnpp/* in order to derive a list of
> orphaned and RF{A,H}ed bugs. Not sure that it's worth rewriting the code
> given how frequently it's likely to be called.

I think it will be called more and more and would certainly be better
served with SOAP interaction instead of HTML parsing in the long run.

Cheers

Luk


-- 
To unsubscribe, send mail to [EMAIL PROTECTED]

Reply via email to