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 |
| -r2 (network-uri-flag-0.1-r2) |
2016-08-27T08:46:34Z |
HerbertValerioRiedel |
b35cdf41ffe29683d1edd38e1226a343e60fa3ea6fc7307a78b7528b24c042ed
|
|
Changed description
from This empty package does not provide any modules; its sole purpose is to
provide the @network-uri@ Cabal flag logic below so you don't have to include
that boilerplate in 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
This avoids combining
@network-uri >= 2.6@ with @network < 2.6@ which both export a
name-clashing @Network.URI@ module, because
in network-2.6 the @Network.URI@ module was split off from the
network package into network-uri-2.6.
In other words, the logic above makes sure that the @Network.URI@ module
is provided by either @network-uri@ or by @network@
(in the <https://en.wikipedia.org/wiki/Exclusive_or XOR> sense).
In order to benefit from this module, simply include it in your
@build-depends@ declaration alongside @network@ and @network-uri@.
> build-depends:
> network >= 2.5 && < 2.7,
> network-uri >= 2.6 && < 2.7,
> network-uri-flag == 0.1.*
/NOTE: It's almost always an error to list this package if network and network-uri aren't both listed as well!/
to This empty package does not provide any modules; its sole purpose is to
provide the @network-uri@ Cabal flag logic below so you don't have to include
that boilerplate in 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
This avoids combining
@network-uri >= 2.6@ with @network < 2.6@ which both export a
name-clashing @Network.URI@ module, because
in network-2.6 the @Network.URI@ module was split off from the
network package into network-uri-2.6.
In other words, the logic above makes sure that the @Network.URI@ module
is provided by either @network-uri@ or by @network@
(in the <https://en.wikipedia.org/wiki/Exclusive_or XOR> sense).
In order to benefit from this module, simply include it in your
@build-depends@ declaration alongside @network@ and @network-uri@.
> build-depends:
> network >= 2.5 && < 2.7,
> network-uri >= 2.5 && < 2.7,
> network-uri-flag == 0.1.*
/NOTE: It's almost always an error to list this package if network and network-uri aren't both listed as well!/
|
| -r1 (network-uri-flag-0.1-r1) |
2016-08-27T08:45:53Z |
HerbertValerioRiedel |
c0668601b7be4d36afb8b00bee14b476ae3acec8909590806ff50283dda14be2
|
|
Changed description
from This empty package does not provide any modules; its sole purpose is to
provide the @network-uri@ Cabal flag logic below so you don't have to include
that boilerplate in 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
This avoids combining
@network-uri >= 2.6@ with @network < 2.6@ which both export a
name-clashing @Network.URI@ module, because
in network-2.6 the @Network.URI@ module was split off from the
network package into network-uri-2.6.
In other words, the logic above makes sure that the @Network.URI@ module
is provided by either @network-uri@ or by @network@
(in the <https://en.wikipedia.org/wiki/Exclusive_or XOR> sense).
In order to benefit from this module, simply include it in your
@build-depends@ declaration alongside @network@ and @network-uri@.
> build-depends:
> network >= 2.5 && < 2.7,
> network-uri >= 2.7 && < 2.8,
> network-uri-flag == 0.1.*
/NOTE: It's almost always an error to list this package if network and network-uri aren't both listed as well!/
to This empty package does not provide any modules; its sole purpose is to
provide the @network-uri@ Cabal flag logic below so you don't have to include
that boilerplate in 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
This avoids combining
@network-uri >= 2.6@ with @network < 2.6@ which both export a
name-clashing @Network.URI@ module, because
in network-2.6 the @Network.URI@ module was split off from the
network package into network-uri-2.6.
In other words, the logic above makes sure that the @Network.URI@ module
is provided by either @network-uri@ or by @network@
(in the <https://en.wikipedia.org/wiki/Exclusive_or XOR> sense).
In order to benefit from this module, simply include it in your
@build-depends@ declaration alongside @network@ and @network-uri@.
> build-depends:
> network >= 2.5 && < 2.7,
> network-uri >= 2.6 && < 2.7,
> network-uri-flag == 0.1.*
/NOTE: It's almost always an error to list this package if network and network-uri aren't both listed as well!/
|
| -r0 (network-uri-flag-0.1-r0) |
2016-08-27T08:44:41Z |
HerbertValerioRiedel |
7c9ab5033dec64d94c0ca0401506ca2a2e72b74852b6961eab60de5f45fe4347
|
|
|