Difference between revisions of "Himerge"
(Add packages to unmask via keywords) |
|||
Line 9: | Line 9: | ||
- High-Emerge |
- High-Emerge |
||
- Himerge Is (only) emerge |
- Himerge Is (only) emerge |
||
+ | |||
+ | '''How do I install Himerge?''' |
||
+ | |||
+ | Since emerge is the Gentoo package manager, these instructions are unlikely to work on any other distro/OS unless of course you have installed [http://www.gentoo.org/proj/en/gentoo-alt/prefix/index.xml prefixed portage]. |
||
+ | |||
+ | You need to unmask several packages, by putting the following in /etc/portage/package.keywords to run the 'unstable' branch. Note that these are actually developed in the [http://www.haskell.org/~gentoo/gentoo-haskell/ haskell overlay] before moving to the portage tree. |
||
+ | |||
+ | <pre> |
||
+ | # haskell |
||
+ | dev-lang/ghc |
||
+ | dev-haskell/cabal |
||
+ | # haskell deps |
||
+ | dev-haskell/mtl |
||
+ | dev-haskell/filepath |
||
+ | dev-haskell/regex-base |
||
+ | dev-haskell/regex-posix |
||
+ | dev-haskell/regex-compat |
||
+ | |||
+ | # himerge |
||
+ | app-portage/himerge |
||
+ | dev-haskell/parallel |
||
+ | dev-haskell/gtk2hs |
||
+ | </pre> |
||
+ | If you're currently running stable ghc, you should upgrade ghc first and then run ghc-updater. Either way, it would be good to emerge ghc first, then emerge himerge. |
Revision as of 12:05, 9 February 2008
This wiki site is supposed to be the place containing all the possible information and documentation for Himerge
FAQs
What does Himerge really/exactly stands for?
It technically stands for "Haskell Interface for eMerge" ; though I personally can also think about some funny terms like:
- Hi 'emerge' - High-Emerge - Himerge Is (only) emerge
How do I install Himerge?
Since emerge is the Gentoo package manager, these instructions are unlikely to work on any other distro/OS unless of course you have installed prefixed portage.
You need to unmask several packages, by putting the following in /etc/portage/package.keywords to run the 'unstable' branch. Note that these are actually developed in the haskell overlay before moving to the portage tree.
# haskell dev-lang/ghc dev-haskell/cabal # haskell deps dev-haskell/mtl dev-haskell/filepath dev-haskell/regex-base dev-haskell/regex-posix dev-haskell/regex-compat # himerge app-portage/himerge dev-haskell/parallel dev-haskell/gtk2hs
If you're currently running stable ghc, you should upgrade ghc first and then run ghc-updater. Either way, it would be good to emerge ghc first, then emerge himerge.