Skip to content

Commit

Permalink
Separate out stackage-curator
Browse files Browse the repository at this point in the history
  • Loading branch information
snoyberg committed Mar 22, 2015
1 parent 8f95d18 commit 1891c1b
Show file tree
Hide file tree
Showing 30 changed files with 9 additions and 4,383 deletions.
9 changes: 0 additions & 9 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,13 +1,4 @@
dist
*.o
*.hi
*.chi
*.chs.h
*.swp
/builds/
/logs/
/.cabal-sandbox/
cabal.sandbox.config
nightly-*.yaml
lts-*.yaml
/tarballs/
64 changes: 0 additions & 64 deletions ChangeLog.md

This file was deleted.

25 changes: 0 additions & 25 deletions Dockerfile

This file was deleted.

12 changes: 8 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,14 @@ __NOTE__ This repository is for package authors to get their code into
Stackage. If you simply want to use Stackage as an end user, please follow the
instructions on [http://www.stackage.org/](http://www.stackage.org).

A note about the codebase: the goal is to minimize dependencies and have
the maximum range of supported compiler versions. Therefore, we avoid
anything "complicated." For example, instead of using the text package,
we use Strings everywhere.
The Stackage project consists of multiple repositories. This repository
contains the metadata on packages to be included in future builds and some
project information. In addition, we have the following repositories:

* [stackage-server](https://github.com/fpco/stackage-server)
* [stackage-curator](https://github.com/fpco/stackage-curator)
* [stackage-types](https://github.com/fpco/stackage-types)
* [lts-haskell](https://github.com/fpco/lts-haskell)

Get your package included
-------------------------
Expand Down
2 changes: 0 additions & 2 deletions Setup.hs

This file was deleted.

234 changes: 0 additions & 234 deletions Stackage/BuildConstraints.hs

This file was deleted.

Loading

0 comments on commit 1891c1b

Please sign in to comment.