Opened 14 years ago

Last modified 13 years ago

#28865 closed update

p5-libwww-perl: new version 6.02, which is now in multiple modules distributed separately — at Version 5

Reported by: l2g@… Owned by: l2g@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: ryandesign@…
Port: p5-libwww-perl

Description (last modified by l2g@…)

Gisle Aas broke up the libwww-perl distribution into multiple distributions. (About time?)

So here is the new libwww-perl 6.x family:

Read the Changes file in libwww-perl, as it mentions some changes with potential to break compatibility in existing scripts that use LWP.

I've played with making portfiles for all of these and can attach them here.

UPDATE (v6.02): To avoid having to install SSL-related files unless they are really needed (I think?), LWP::Protocol::https is now distributed separately as well.

Change History (5)

comment:1 in reply to:  description Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added

Replying to l2g@…:

This portfile was submitted in #29540 and I cleaned it up a bit.

I've played with making portfiles for all of these and can attach them here.

Larry, if you can commit these updates, that would be great. Matthew appears to be busy with other things.

comment:2 Changed 13 years ago by l2g@…

Owner: changed from narf_tm@… to l2g@…

I need a little advice on this. Since there will be multiple ports containing the same files as the current p5-libwww-perl port contains, there is a catch-22 when upgrading. MacPorts starts upgrading p5-libwww-perl, then sees the new dependencies. So it tries to bring in the dependencies first. As soon as it hits a port with files overlapping the original p5-libwww-perl, there's a file conflict and the upgrade halts with an error.

This can be worked around by deactivating p5-libwww-perl first, but how best to tell the admin to do that? Or is there a better way to handle something like this?

comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

I think at this time the best option is the awful pre-activate registry_deactivate hack employed by a handful of ports. See examples in r75570, r74956, r72540.

comment:4 in reply to:  3 Changed 13 years ago by l2g@…

Status: newassigned

Replying to ryandesign@…:

I see what you mean; it's a bit of a kludge. But I like it better. I'll work on that.

comment:5 Changed 13 years ago by l2g@…

Description: modified (diff)
Summary: p5-libwww-perl: new version 6.01, which is now in multiple modules distributed separatelyp5-libwww-perl: new version 6.02, which is now in multiple modules distributed separately

Caught one more wrinkle at the last minute. Since libwww-perl 6.02 was released, Mr. Aas has decided to distribute LWP-UserAgent-https separately as well. So, one more port...

Note: See TracTickets for help on using tickets.