| 1 |
On Wed, 2003-04-02 at 12:14, Peter Simons wrote: |
| 2 |
> Now we wonder how to organize this in the ebuild. A virtual |
| 3 |
> "haskell-compiler" target won't do us any good, because -- as I said |
| 4 |
> -- many packages require ghc. Hard-coding the ebuilds to depend on ghc |
| 5 |
> only is not the right thing to do either, because some packages _can_ |
| 6 |
> be build with either ghc or nhc, and ideally, the user would be able |
| 7 |
> to choose which compiler should be used. |
| 8 |
|
| 9 |
You could create virtual/haskellc (or virtual/hc or whatever) and |
| 10 |
packages could then depend on any of: |
| 11 |
o virtual/haskellc |
| 12 |
o dev-lang/ghc |
| 13 |
o dev-lang/nhc98 |
| 14 |
according to their compiler requirements. |
| 15 |
|
| 16 |
If you want to give the user the choice of which compiler to use (for |
| 17 |
packages that could be built with either compiler) then provide a tool, |
| 18 |
along the lines of gcc-config, which either creates symlinks or plays |
| 19 |
around with the path to select one of these compilers. |
| 20 |
|
| 21 |
HTH, |
| 22 |
|
| 23 |
- olly |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives