Description: ------------ Not sure why Net_URL_Mapper depends on it, but here's an update to Net_URL2.

Added patch Mapper.patch.

Does this package even use Net_URL? If not, drop it from the package.xml perhaps?

Yes i am using net_url and i prefer the first version to the second

if it ain't broken, don't fix it...

Any particular reason why you prefer Net_URL over Net_URL2? If a feature is missing, we can probably port it to Net_URL2.Net_URL is superceeded by Net_URL2.

under error_reporting(E_ALL | E_STRICT), it throws 'Non-static method Net_URL::resolvePath() should not be called statically, assuming $this from incompatible context'. Changing calls from Net_Url::resolvePath() to the (ostensibly) functionally identical Net_Url2::removeDotSegments() would resolve this.

Hey Bertrand, do you mind updating? :-) We could help with the transition too, or fix something in Net_URL2 if it's required. Till

Hi Till, I'm a bit short on time right now but I don't think the transition will be too difficult so if you want to give it a try, be my guest. I suggest we make a PHP5 only package, call it Net_URL2_Mapper and release. There are other things to do as well, but they can wait.

The package is not yet stable (version-wise) so we don't have to create Net_URL2_Mapper. I would just adjust the dependency and move from Net_URL to Net_URL2. None of the behavior (e.g. user-facing API) must change for this. :-)

OK, if it doesn't break API, then it's fine.

Can we just apply this patch then?