Update docs
This commit is contained in:
parent
640cf1e2c1
commit
ee9b2ec30d
12
HACKING.md
12
HACKING.md
@ -43,3 +43,15 @@ Kazu Yamamoto [explained it in his PR](https://github.com/yesodweb/wai/pull/752#
|
|||||||
1. Brittany
|
1. Brittany
|
||||||
2. mtl-style preferred
|
2. mtl-style preferred
|
||||||
3. no overly pointfree style
|
3. no overly pointfree style
|
||||||
|
|
||||||
|
## Code structure
|
||||||
|
|
||||||
|
Main functionality is in `GHCup` module. Utility functions are
|
||||||
|
organised tree-ish in `GHCup.Utils` and `GHCup.Utils.*`.
|
||||||
|
|
||||||
|
Anything dealing with ghcup specific directories is in
|
||||||
|
`GHCup.Utils.Dirs`.
|
||||||
|
|
||||||
|
Download information on where to fetch bindists from is in
|
||||||
|
`GHCup.Data.GHCupDownloads`.
|
||||||
|
|
||||||
|
11
README.md
11
README.md
@ -68,11 +68,14 @@ handles your haskell packages and can demand that [a specific version](https://c
|
|||||||
For man pages to work you need [man-db](http://man-db.nongnu.org/) as your `man` provider, then issue `man ghc`. Manpages only work for the currently set ghc.
|
For man pages to work you need [man-db](http://man-db.nongnu.org/) as your `man` provider, then issue `man ghc`. Manpages only work for the currently set ghc.
|
||||||
`MANPATH` may be required to be unset.
|
`MANPATH` may be required to be unset.
|
||||||
|
|
||||||
### Bash-completion
|
### Shell-completion
|
||||||
|
|
||||||
Depending on your distro and setup, install `.bash-completion` from this repo
|
Shell completions are in `shell-completions`.
|
||||||
as e.g. `/etc/bash_completion.d/ghcup` and make sure your bashrc sources the
|
|
||||||
startup script (`/usr/share/bash-completion/bash_completion` on some distros).
|
For bash: install `shell-completions/bash`
|
||||||
|
as e.g. `/etc/bash_completion.d/ghcup` (depending on distro)
|
||||||
|
and make sure your bashrc sources the startup script
|
||||||
|
(`/usr/share/bash-completion/bash_completion` on some distros).
|
||||||
|
|
||||||
## Design goals
|
## Design goals
|
||||||
|
|
||||||
|
@ -4,8 +4,11 @@
|
|||||||
|
|
||||||
2. Add/fix downloads to `GHCupDownloads` module, then run `ghcup-gen gen` to generate the new json and validate it via `ghcup-gen check`.
|
2. Add/fix downloads to `GHCupDownloads` module, then run `ghcup-gen gen` to generate the new json and validate it via `ghcup-gen check`.
|
||||||
|
|
||||||
3. Commit and git push with tag. Wait for tests to succeed.
|
3. Commit and git push with tag. Wait for tests to succeed and release artifacts to build.
|
||||||
|
|
||||||
4. Upload the new `ghcup-<ver>.json` to `webhost.haskell.org/ghcup/data/`.
|
4. Download release artifacts and upload them `downloads.haskell.org/ghcup`
|
||||||
|
|
||||||
|
5. Add release artifacts to GHCupDownloads (see point 2.)
|
||||||
|
|
||||||
|
6. Upload the final `ghcup-<ver>.json` to `webhost.haskell.org/ghcup/data/`.
|
||||||
|
|
||||||
5. Build ghcup releases for Linux (fully static), mac (with `-fcurl`) and FreeBSD (with `-fcurl`). Upload to `webhost.haskell.org/ghcup/bin/` and update symlinks.
|
|
||||||
|
Loading…
Reference in New Issue
Block a user