property-list: XML property list parser
Parser, data type and formatter for Apple's XML property list 1.0 format. The bytestring-0.9.1.5 update on hackage seems to have cratered the build for many packages, including the last several versions of this one, so this version will probably not build properly on the hackage site. As far as I know, though, that is the only reason it fails. This version includes a hack to try to make it build on the site, triggered by the HaXml_1_13 build flag.
|Versions||0.0.0.1, 0.0.0.1.1, 0.0.0.3, 0.0.0.4, 0.0.0.5, 0.0.0.6, 0.0.0.7, 0.0.1.0, 0.0.3, 0.1, 0.1.0.1, 0.1.0.2, 0.1.0.3, 0.1.0.4, 0.1.0.5|
|Dependencies||base (>=3 && <5), bytestring, bytestring-class, containers, data-object, dataenc, HaXml (==1.13.* || >=1.19), mtl, old-locale, pretty, template-haskell (<2.6), th-fold, time, utf8-string (==0.3.5) [details]|
|Author||James Cook <firstname.lastname@example.org>|
|Maintainer||James Cook <email@example.com>|
|Category||Data, Parsing, XML|
|Uploaded||by JamesCook at Thu Dec 10 16:56:39 UTC 2009|
|Downloads||5582 total (7 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI
Use the new version of the data-object package (>= 0.0.2) Which has a "generic object" type in place of the simpler Object type in previous versions.
Template Haskell 2.4 seems to have made the
The Hackage website builder is currently very finicky and the bytestring-0.9.1.5 update has made me very frustrated, because the last several versions of this package have failed to build because of it. The "preferred-versions" fallback fails too, because the additional HaXml constraint combined with the one here becomes unsatisfiable. So, I'm gonna make this thing work with HaXml 1.13 now. And, as an additional hack to make sure it works, this flag will also trigger dependencies on specific versions of packages known to have been built against bytestring-0.9.1.4 on the hackage server. Once ghc-6.12 is released, this should no longer be a problem and I can clean up the mess I've made here.
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
For package maintainers and hackage trustees