Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
No. |
Time |
User |
SHA256 |
-r1 (network-uri-2.6.4.0-r1) |
2021-02-13T02:13:06Z |
EzraCooper |
519497b268fab8a1872ba8668efcecbc9d7b3200a2f8a9140eabcce3e840c590
|
|
Changed description
from This package provides facilities for parsing and unparsing URIs, and creating
and resolving relative URI references, closely following the URI spec,
<http://www.ietf.org/rfc/rfc3986.txt IETF RFC 3986>.
== Backward-compatibility
In @network-2.6@ the "Network.URI" module was split off from the
@network@ package into this package. If you're using the "Network.URI"
module you can be backward compatible and automatically get it from
the right package by using the
</package/network-uri-flag network-uri-flag pseudo-package>
in your @.cabal@ file's build-depends (along with dependencies for
both @network-uri@ and @network@):
> build-depends:
> network-uri-flag == 0.1.*
Or you can do the same manually by adding this boilerplate to your
@.cabal@ file:
> flag network-uri
> description: Get Network.URI from the network-uri package
> default: True
>
> library
> -- ...
> if flag(network-uri)
> build-depends: network-uri >= 2.6, network >= 2.6
> else
> build-depends: network-uri < 2.6, network < 2.6
That is, get the module from either @network < 2.6@ or from
@network-uri >= 2.6@.
to NOTE: Version 2.6.4.0 accidentally released a version that was not marked as
"Safe", although the module is Safe, thus breaking compatibility, and so
version 2.6.4.0 is given the dependency "base < 0" to forcibly deprecate it.
Use 2.6.4.1 instead.
This package provides facilities for parsing and unparsing URIs, and creating
and resolving relative URI references, closely following the URI spec,
<http://www.ietf.org/rfc/rfc3986.txt IETF RFC 3986>.
== Backward-compatibility
In @network-2.6@ the "Network.URI" module was split off from the
@network@ package into this package. If you're using the "Network.URI"
module you can be backward compatible and automatically get it from
the right package by using the
</package/network-uri-flag network-uri-flag pseudo-package>
in your @.cabal@ file's build-depends (along with dependencies for
both @network-uri@ and @network@):
> build-depends:
> network-uri-flag == 0.1.*
Or you can do the same manually by adding this boilerplate to your
@.cabal@ file:
> flag network-uri
> description: Get Network.URI from the network-uri package
> default: True
>
> library
> -- ...
> if flag(network-uri)
> build-depends: network-uri >= 2.6, network >= 2.6
> else
> build-depends: network-uri < 2.6, network < 2.6
That is, get the module from either @network < 2.6@ or from
@network-uri >= 2.6@. Changed the library component's library dependency on 'base'
from >=3 && <5
to <0
|
-r0 (network-uri-2.6.4.0-r0) |
2021-02-07T19:55:10Z |
EzraCooper |
6109c4b66a840bd2939bb3b6c79dc7d6e83ea05f3d53fb9fe45802db8f416fa4
|
|
|