Difference between revisions of "Haskell Platform"

Revision as of 13:16, 12 May 2013

The Haskell Platform is a single, standard Haskell development environment for everyone. It offers a set of blessed libraries and tools, to save you the task of picking and choosing which core Haskell libraries to use.

Learn more about the Haskell Platform ⇒

What's in the platform

See

the change log
the unofficial Versions Comparison Chart

Trouble shooting

The Haskell Platform project maintains a bug tracker and wiki site, which you can use to report problems, or request features:

Developers

For developers, there is a wiki page with project details:

Buttons

We have some buttons to let your friends know about the Haskell Platform.

Use this html in your site:

<a href="http://hackage.haskell.org/platform" ><img src="http://hackage.haskell.org/platform/icons/button-100.png"></a>

Use this html in your site:

<a href="http://hackage.haskell.org/platform" ><img src="http://hackage.haskell.org/platform/icons/button-64.png"></a>

SVG source for the button: http://haskell.org/haskellwiki/Image:Button.svg

Icons

Icons for the platform installer and desktop.

Legal

The cherry blossom image used in the 2011 HP release is licensed CC by tanakawho

@@ Line 1: / Line 1: @@
+{{HP}}
-'''Haskell: Batteries Included'''
+The Haskell Platform is a single, standard [[Haskell]] development environment for everyone. It offers a set of blessed libraries and tools, to save you the task of picking and choosing which core Haskell libraries to use.
-The Haskell Platform (HP) is the name of a proposed library set
-that would be the minimum standard for Haskell library support on a
-system.
+[http://hackage.haskell.org/platform/contents.html Learn more about the Haskell Platform ⇒]
-More generally, if we want tools as well as libraries, then the simpler name
-''Haskell Platform'' may be more appropriate.
+__TOC__
-There are now more than 500 libraries available for Haskell,  on
-[http://hackage.haskell.org hackage]. Choosing which libraries to
-support on a distro is currently done on an ad hoc basis, with
-significant variation from one distribution to another.
+== What's in the platform ==
-Some, such as Arch Linux, or Gentoo Linux, include as many libraries as
-possible (typically over 400), while others have the bare minimum
-required to build ghc and say, darcs and xmonad.
+See
-The Haskell community needs to provide direction and blessing to a
+* the [http://hackage.haskell.org/platform/changelog.html change log]
-library set that should be available and adopted, to further encourage
+* the unofficial [http://sol.github.com/haskell-platform-versions-comparison-chart/ Versions Comparison Chart]
-Haskell use.
-Ensuring that the chosen set of library versions works well together, and
-with a particular version of GHC (and other tools), is a major goal.
-== Discussion ==
+== Trouble shooting ==
+The Haskell Platform project maintains a bug tracker and wiki site, which you can use to report problems, or request features:
-* [http://thread.gmane.org/gmane.comp.lang.haskell.cvs.ghc/28062/focus=28807 A discussion] took place in June and July 2008 about the direction of the HLP.
-* [http://haskell.org/~duncan/ghc/%23ghc-2008-07-16.log More occured during the #ghc meeting]
+* [http://trac.haskell.org/haskell-platform/report/1 Known issues]
-== Next Steps==
+* [http://trac.haskell.org/haskell-platform/newticket?summary=%3CProblem%3E&description=%3CDescribe%20the%20problem%3E&component=Platform Report a bug]
-The next step in the process:
+=== Developers ===
-* Define admission progress: how does a package get into the HLP
-* Sort out the release team
-* Define the installation expectations
-* Set up a bug tracker for the HLP project.
-* Create a repo.
+For developers, there is a wiki page with project details:
-==Criteria==
+* [http://trac.haskell.org/haskell-platform/ Developer's wiki]
-* GHC would build against its own core libraries, but would be generally distributed with the HLP.
+* [http://trac.haskell.org/haskell-platform/wiki/ReleaseTimetable Release Timetable]
-* The HLP should provide good coverage for all typical tasks one might want to accomplish with the language, given library availability.
+== Buttons ==
-* No bottlenecks: release of the HLP should be entirely independent from GHC, and also independent of the development cycle of any individual library or tool.
+We have some buttons to let your friends know about the Haskell Platform.
-===Quality Control===
+[http://hackage.haskell.org/platform http://hackage.haskell.org/platform/icons/button-100.png]
-* cabal-installable libraries with haddocks.
-* The set of HP packages + core libs must be closed. That is all haskell dependencies must be from within the HP packages or core libs. Dependencies on C libs can be external.
-* All packages in a particular HP version must have a consistent install plan.
-  That means only one version of each package and all dependencies on packages must be satisfied by the version in the HP package set.
+Use this html in your site:
-There is code in cabal-install to check the last two requirements.
+<code>
-Other possible ideas for quality standards we might want to require:
+<nowiki>
+<a href="http://hackage.haskell.org/platform"
+><img src="http://hackage.haskell.org/platform/icons/button-100.png"></a>
+</nowiki>
+</code>
+[http://hackage.haskell.org/platform http://hackage.haskell.org/platform/icons/button-64.png]
-* exposed module names must follow the hierarchical module name convention, meaning they must be in an appropriate place in the module namespace.
+Use this html in your site:
-== Current library set ==
+<code>
-===Core system===
+<nowiki>
+<a href="http://hackage.haskell.org/platform"
+><img src="http://hackage.haskell.org/platform/icons/button-64.png"></a>
+</nowiki>
+</code>
+SVG source for the button: http://haskell.org/haskellwiki/Image:Button.svg
-This will be on every system, as they're required for GHC to build:
-* array
-* base
-* bytestring
-* Cabal
-* containers
-* directory
-* editline
-* filepath
-* haskell98
-* hpc
-* integer-gmp
-* old-locale
-* old-time
-* packedstring
-* pretty
-* process
-* random
-* template-haskell
-* unix OR Win32
-===Extra libraries===
+=== Icons ===
+Icons for the platform installer and desktop.
-Current libraries available in the 'extralibs' bundle provided with GHC,
-a descendent of what used to by fptools, with a few additions.
+[[Image:Platform-100.png]]
-*   ALUT
-*   GLUT
-*   HUnit
-*   ObjectIO
-*   OpenAL
-*   OpenGL
-*   QuickCheck
-*   cgi
-*   fgl
-*   haskell-src
-*   html
-*   mtl
-*   network
-*   parsec
-*   parallel
-*   regex-base
-*   regex-compat
-*   regex-posix
-*   stm
-*   time
-*   xhtml
+[[Image:Platform-64.png]]
-== HLP: Batteries Included==
-[[/Batteries_Included]]
-== Tools ==
+=== Legal ===
+* The cherry blossom image used in the 2011 HP release is [http://www.flickr.com/photos/28481088@N00/3291086383/ licensed CC by tanakawho]
-Language-processing tools should probably also be considered to be part of the platform.  Commonly-needed tools include:
-* ghc
-* happy
-* alex
-* haddock
-* cpphs
-* cabal-install (now known simply as cabal?)
+[[Category:HaskellPlatform]]
-What else might we consider?
-* DrIFT or derive
-* throw in another compiler - e.g. Hugs?
-* c2hs
-* hsc2hs
-==Release mechanics==
-==Public "Haskell Platform Compliant" list==
-To encourage adoption of the HLP, distributions that support the HLP
-will be publically listed as e.g. "Haskell Platform Compliant"
-==History==
-* fptools
-* extralibs/ core libs
-== Related ==
-* [http://docs.python.org/lib/lib.html Python libraries]
-* [http://live.gnome.org/ReleasePlanning Gnome's release process]
-* [http://live.gnome.org/ReleasePlanning/ModuleProposing How to propose modules for GNOME]
-[[Category:Community]]