Bug#604934: libproxy: Please upgrade to 0.46

[Iain Lane]

retitle 604394 Upgrade to 0.4 series
thanks

On Thu, Nov 25, 2010 at 04:39:32PM +0100, Artur Rona wrote:
> Package: libproxy
> Version: 0.3.1-2
> 
> Please upgrade libproxy to latest upstream version (ATM is 0.46).
> Current version is out-of-dated.

I've been working recently on upgrading libproxy to 0.47, the latest
upstream. My work is in

  git://anonscm.debian.org/users/laney/libproxy.git

but I'll merge it into SVN when it's ready to be released.

I've split the package quite a lot and put all of the modules in their
own packages because some of them have quite long dependency chains that
users don't need.

I don't know what the best way to get the modules out to users is
though. Have them come in as part of the tasks?

Then there's the question of the pacrunner modules which interpret the
javascript .pac files which some users will be using. There are two of
those - mozjs and webkit, with obvious dependencies. I suspect some
users won't be very happy about having the wrong one of those.

Other than this question of how to get the environment-appropriate
dependencies out to users, the packaging seems mostly OK from my side.
I'd appreciate reviews though.

Regards,

-- 
Iain Lane                                  [ iain at orangesquash.org.uk ]
Debian Developer                                   [ laney at debian.org ]
Ubuntu Developer                                   [ laney at ubuntu.com ]
PhD student                                       [ ial at cs.nott.ac.uk ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20110922/d2233d76/attachment.pgp>