Metadata revisions for network-uri-2.6.1.0

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.1.0-r1) 2017-06-08T08:12:39Z HerbertValerioRiedel 62cc45c66023e37ef921d5fb546aca56a9c786615e05925fb193a70bf0913690
  • Changed description from

    This package provides an URI manipulation interface.
    
    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 automatically get it from the right package by adding
    this 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
    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@.

-r0 (network-uri-2.6.1.0-r0) 2016-03-19T21:12:16Z EzraCooper fd8a39c99060632e6bb106e36e3e6cfbf57e420b4cf998bd6087529ac339b64d